On Sun, Aug 10, 2008 at 7:18 AM, Stefan Behnel <[EMAIL PROTECTED]> wrote: > Hi, > > I wonder why the ElementTree modules in Py3k's xml.etree still do not follow > PEP8 naming (ok, besides the obvious explanation that no-one renamed them so > far). Was there a decision that they should keep their name despite the > general push towards a uniformly named standard library? Or would it be ok to > rename them for the next beta?
The stdlib APIs are never going to be completely PEP 8 compliant, and that's ok; internal consistency (in the library) is most important. I'm very -1 this late in the release cycle. > > Given the fact that most packages that depend on ET already use more than one > try-except import for these modules anyway (and likely a separate module that > cares for the right import), I don't see the situation becoming any worse by > making them PEP8 compliant. > > Stefan > > _______________________________________________ > Python-3000 mailing list > Python-3000@python.org > http://mail.python.org/mailman/listinfo/python-3000 > Unsubscribe: > http://mail.python.org/mailman/options/python-3000/musiccomposition%40gmail.com > -- Cheers, Benjamin Peterson "There's no place like 127.0.0.1." _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
