> 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?
There was no such push (some people where pushing, but they were fortunately stopped). > Or would it be ok to rename them for the next beta? Definitely not. The policy is to not gratuitously break things. > 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. So what specific changes would you have in mind? How would existing code have to be changed to accommodate these changes? Regards, Martin _______________________________________________ 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
