Movatterモバイル変換
[0]ホーム
[Python-Dev] folding cElementTree behind ElementTree in 3.3
Stefan Behnelstefan_ml at behnel.de
Fri Feb 10 11:44:11 CET 2012
"Martin v. Löwis", 10.02.2012 10:37:>> Given that it was two months ago that I started the "Fixing the XML>> batteries" thread (and years since I brought up the topic for the first>> time), it seems to be hard enough already to get anyone on python-dev>> actually do something for Python's XML support, instead of just actively>> discouraging those who invest time and work into it.>> It depends on the nature of the changes you want to see done. Just> bashing some piece of code is not something that I personally consider> a worthwhile thing, so I'll likely continue to discourage changes in> a direction that demeans some XML library in favor of some other.This is getting off-topic for this thread, but anyway. What I meant with myparagraph above was that none of the topics I brought up has received anyaction on the side of those with commit rights yet, regardless of howobvious they were and how much or little dispute there was about them.IMHO, all of this boils down to whether or not we should make it easier forusers to efficiently use the stdlib. Backing ElementTree by the acceleratormodule helps here, and fixing the docs to point (new) users to ElementTreeinstead of MiniDOM helps as well.I can happily accept that you have a different opinion on the latter topicthan I do. What I cannot accept is that, as we speak, this leads to usersgetting drawn into using the wrong tool for their job, into wasting theirtime (both for development and runtime) and potentially into getting drawnaway from the (IMHO) perfect language for XML processing.I don't think bashing is the right word here. Everyone who, knowing thealternatives, decides to use MiniDOM is welcome to do so. I'm just stating,both from my personal experience and from discussions on c.l.py, that thecurrent documentation makes it easier for new users to take the wrongdecision for them than to make this decision in an informed way. MiniDOM*may* be the right thing further down along the way in some cases. It'salmost *never* the right thing to start with, simply because if you do, itinherently takes way too much time until you reach the point where theevidence becomes obvious that it actually was the wrong decision. Thedocumentation should allow innocent users to see this risk clearly beforethey start wasting their time.So, getting back to the topic again, is there any reason why you wouldoppose backing the ElementTree module in the stdlib by cElementTree'saccelerator module? Or can we just consider this part of the discussionsettled and start getting work done?Stefan
More information about the Python-Devmailing list
[8]ページ先頭