➜

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, flox, jcea, jkloth, ncoghlan, python-dev, scoder
Date 2013-08-26.07:50:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377503441.48.0.682794762275.issue17741@psf.upfronthosting.co.za>
In-reply-to
Content 
> iterparse's "parser" argument will be deprecated

No need to do that. Update the docs, yes, but otherwise keep the possibility to improve the implementation later on, without going through a deprecation + dedeprecation cycle. That would just confuse users IMHO.
History
Date User Action Args
2013-08-26 07:50:41scodersetrecipients: + scoder, jcea, ncoghlan, jkloth, eli.bendersky, flox, python-dev
2013-08-26 07:50:41scodersetmessageid: <1377503441.48.0.682794762275.issue17741@psf.upfronthosting.co.za>
2013-08-26 07:50:41scoderlinkissue17741 messages
2013-08-26 07:50:41scodercreate