A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2013-August/127859.html below:

[Python-Dev] xml.etree.ElementTree.IncrementalParser

[Python-Dev] xml.etree.ElementTree.IncrementalParserAntoine Pitrou solipsis at pitrou.net
Fri Aug 9 14:50:50 CEST 2013
Le Fri, 09 Aug 2013 13:11:11 +0200,
Stefan Behnel <stefan_ml at behnel.de> a écrit :
> 
> I attached it to the ticket that seems to have been the source of this
> addition.
> 
> http://bugs.python.org/issue17741
> 
> Please note that the tulip mailing list is not an appropriate place to
> discuss additions to the XML libraries, and ElementTree in particular.

Well, the bug tracker is the main point of discussion, except that few
people bothered discussing it.

> Is there a way to get automatic notification when the XML component is
> assigned to a ticket? (Not that it would have helped in this case, as
> the component was missing from the ticket.)

You could ask to get included in the "experts" index:
http://docs.python.org/devguide/experts.html
(I doubt anyone would object to that)

> Anyway, given that there isn't really the One Obvious Way to do it,
> maybe you should just add a docstring to the class (ahem), reference
> the stream protocol as the base for its API, and then rename it to
> IncrementalStreamParser.

I don't think there's any point in making the class name longer.
Parsing XML incrementally is pretty much what it does.
As for the docstring, uh, well, sure :-)

(IMHO, IncrementalParser is the One Obvious Way to do incremental XML
parsing in 3.4, but YMMV)

Regards

Antoine.


More information about the Python-Dev mailing list

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