Author scoder
Recipients eli.bendersky, flox, jcea, ncoghlan, python-dev, scoder
Date 2013-08-25.15:35:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377444935.16.0.829001277558.issue17741@psf.upfronthosting.co.za>
In-reply-to
Content
> fully working patches will be considered

Let me remind you that it's not me who wants this feature so badly.


> 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.

If that's your concern, then I suggest not adding the feature at all, as long as we don't know if we can (or should) keep up the IncrementalParser facade with the revised implementation.

For example, can it accept a user defined parser instance as input or not? Can it accept a user defined parser target as input? Can it wrap it or would it maybe have to inherit from a TreeBuilder? Should it be a class or a helper function? I don't see how the interface you proposed leaves less questions open than what I am proposing.
History
Date User Action Args
2013-08-25 15:35:35scodersetrecipients: + scoder, jcea, ncoghlan, eli.bendersky, flox, python-dev
2013-08-25 15:35:35scodersetmessageid: <1377444935.16.0.829001277558.issue17741@psf.upfronthosting.co.za>
2013-08-25 15:35:35scoderlinkissue17741 messages
2013-08-25 15:35:34scodercreate