<snip> > """A common pattern in Python 2.x is to have one version of a module > implemented in pure Python, with an optional accelerated version > implemented as a C extension; for example, pickle and cPickle. This > places the burden of importing the accelerated version and falling > back on the pure Python version on each user of these modules. In > Python 3.0, the accelerated versions are considered implementation > details of the pure Python versions. Users should always import the > standard version, which attempts to import the accelerated version and > falls back to the pure Python version. The pickle / cPickle pair > received this treatment. The profile module is on the list for 3.1. > The StringIO module has been turned into a class in the io module.""" > > Is there a good reason why xml.etree.ElementTree / > xml.etree.cElementTree did not "receive this treatment"? > <snip>
Since there appeared to be an overall positive response for making this change in Python 3.3, and since there isn't longer any doubt about the ownership of the package *in Python's stdlib* (see http://mail.python.org/pipermail/python-dev/2012-February/116389.html), I've opened issue 13988 on the bug tracker to follow the implementation. Eli _______________________________________________ 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
