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 scoder
Recipients eli.bendersky, ethan.furman, flox, jcea, jkloth, ncoghlan, python-dev, r.david.murray, scoder
Date 2014-03-11.07:20:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1394522428.38.0.139145931566.issue17741@psf.upfronthosting.co.za>
In-reply-to
Content
My latest status is that a decision on the future of the "parser" argument is still pending. See #20219.

It's correctly deprecated in the sense that passing any previously existing parser isn't going to be supported anymore, but passing an XMLPullParser (which is new in Py3.4 and thus can't have been used in existing code) now makes perfect sense (IMHO). So, in a way, it might end up as a sort of argument recycling rather than argument deletion.
History
Date User Action Args
2014-03-11 07:20:28scodersetrecipients: + scoder, jcea, ncoghlan, jkloth, r.david.murray, eli.bendersky, flox, ethan.furman, python-dev
2014-03-11 07:20:28scodersetmessageid: <1394522428.38.0.139145931566.issue17741@psf.upfronthosting.co.za>
2014-03-11 07:20:28scoderlinkissue17741 messages
2014-03-11 07:20:27scodercreate