This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients dhgutteridge, terry.reedy
Date 2011-08-30.16:35:15
SpamBayes Score 0.00751729
Marked as misclassified No
Message-id <1314722116.33.0.861998460269.issue12829@psf.upfronthosting.co.za>
In-reply-to
Content
My understanding is that what you did:
import xml.parsers.expat
is now the proper way to use expat. After some searching, it seems the sentence about direct use of pyexpat being deprecated refers to
http://sourceforge.net/tracker/?func=detail&aid=2745230&group_id=26590&atid=387667
"The location and name of the PyExpat module have moved in Python v2.6.1 from  xml.dom.ext.reader.PyExpat to xml.parsers.expat"
This is puzzling becasue xmo.parsers.expat dates back to 2.0 while I see no doc for xml.dom.ext... .

The deprecation notice should be deleted from the 3.x docs.
History
Date User Action Args
2011-08-30 16:35:16terry.reedysetrecipients: + terry.reedy, dhgutteridge
2011-08-30 16:35:16terry.reedysetmessageid: <1314722116.33.0.861998460269.issue12829@psf.upfronthosting.co.za>
2011-08-30 16:35:15terry.reedylinkissue12829 messages
2011-08-30 16:35:15terry.reedycreate