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, ethan.furman, flox, jcea, jkloth, ncoghlan, python-dev, scoder
Date 2013-08-27.23:15:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377645320.51.0.0963654486453.issue17741@psf.upfronthosting.co.za>
In-reply-to
Content
W.r.t. the summary in http://bugs.python.org/msg196177, after some further chat with Nick, a name that sounds good for us for the class is XMLPullParser. It has both XML and Parser in it, so the intention is clear. On the other hand, Pull works well for analogy with the existing pull API in xml.dom.pulldom, *and* suggests that the push API is inactive and gets redirected to a pull API (thanks Nick for this insight). 

The method names remain as suggested there.
History
Date User Action Args
2013-08-27 23:15:20eli.benderskysetrecipients: + eli.bendersky, jcea, ncoghlan, scoder, jkloth, flox, ethan.furman, python-dev
2013-08-27 23:15:20eli.benderskysetmessageid: <1377645320.51.0.0963654486453.issue17741@psf.upfronthosting.co.za>
2013-08-27 23:15:20eli.benderskylinkissue17741 messages
2013-08-27 23:15:20eli.benderskycreate