On 25 August 2013 00:13, Antoine Pitrou <solipsis at pitrou.net> wrote: > On Sun, 25 Aug 2013 00:03:01 +1000 > Nick Coghlan <ncoghlan at gmail.com> wrote: >> If Stefan's "please revert this" as lxml.etree maintainer isn't >> enough, then I'm happy to add a "please revert this" as a core >> committer that is confused about how and when the new tulip-inspired >> incremental parsing API should be used in preference to the existing >> incremental parsing API, and believes this needs to be clearly >> resolved before adding a second way to do it >> (especially if there's a >> possibility of using a different implementation strategy that avoids >> adding the second way). > > To be clear, again: anyone who wants to "see it resolved" can take over > the issue and handle it by themselves. I'm done with it. OK, I'll revert it for now, then. If someone else steps up to resolve the API duplication problem, cool, otherwise we can continue to live without this as a standard library feature. Regards, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4