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, ncoghlan, python-dev, scoder
Date 2013-08-25.14:45:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377441949.33.0.412562110107.issue17741@psf.upfronthosting.co.za>
In-reply-to
Content
> I still think IncrementalParser is worth keeping.

If you want to keep it at all cost, I think we should at least hide it behind a function (as with iterparse()). If it's implemented as a class, chances are that people will start relying on internals by inheriting from it. And we already know that those internals should eventually be removed completely. Eventually, that function should become a two-liner or so.
History
Date User Action Args
2013-08-25 14:45:49scodersetrecipients: + scoder, jcea, ncoghlan, eli.bendersky, flox, python-dev
2013-08-25 14:45:49scodersetmessageid: <1377441949.33.0.412562110107.issue17741@psf.upfronthosting.co.za>
2013-08-25 14:45:49scoderlinkissue17741 messages
2013-08-25 14:45:49scodercreate