On 24 August 2013 15:32, Stefan Behnel <stefan...@behnel.de> wrote: > So, to put it more nicely, I think this feature was added without the > amount of review that it needs, and now that I've given it that review, I'm > asking for removal of the feature and a proper redesign that fits into the > existing library.
FWIW, it seems to me that this is something that could live in *tulip* as an adapter between the tulip data processing APIs and the existing ElementTree incremental parsing APIs, without needing to be added directly to xml.etree at all. It certainly seems premature to be adding tulip-inspired APIs to other parts of the standard library, when tulip itself hasn't been deemed ready for inclusion. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
