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 eli.bendersky
Recipients eli.bendersky, flox, jcea, ncoghlan, python-dev, scoder
Date 2013-08-25.15:23:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Stefan, I don't mind looking at a working patch; however, it's not clear to me how you intend to solve the iterparse-accepting-a-custom-XMLParser problem. As for faking the new API, I don't know if that's a good idea because we're not yet sure what that new API is. I agree with your earlier observation that we must begin by refactoring the internals (in the C implementation) and defining cleaner APIs for existing objects. Once we do that, we may have better ideas about the ideal API for incremental parsing / event building. But that's a large job.

Again, fully working patches will be considered. Lacking those, I'm inclined to go with the interim solution proposed in
Date User Action Args
2013-08-25 15:23:37eli.benderskysetrecipients: + eli.bendersky, jcea, ncoghlan, scoder, flox, python-dev
2013-08-25 15:23:37eli.benderskysetmessageid: <>
2013-08-25 15:23:37eli.benderskylinkissue17741 messages
2013-08-25 15:23:37eli.benderskycreate