Message 153056 - Python tracker

Message153056

Author	scoder
Recipients	effbot, eli.bendersky, flox, scoder
Date	2012-02-10.15:37:16
SpamBayes Score	1.482313e-07
Marked as misclassified	No
Message-id	<4F35399A.90408@users.sourceforge.net>
In-reply-to	<1328885577.51.0.77313357168.issue13988@psf.upfronthosting.co.za>

Content
Eli Bendersky, 10.02.2012 15:52: > * The current contents of xml/etree/ElementTree.py will move to xml/etree/pyElementTree.py IIRC, there is a well specified way how accelerator modules should be used by Python modules. I recall a lengthy discussion on python-dev (or the py3k list?) back in the old pre-3.0 days, maybe there's even a PEP? > * xml/etree/cElementTree.py disappears. Careful with backwards compatibility here. It's the accelerator module (_elementtree.so, IIRC) which is to be moved behind ElementTree.py. I don't see a compelling enough reason to break imports in existing code by removing the cElementTree module, so we should not do that. Stefan

Content

Eli Bendersky, 10.02.2012 15:52:
> * The current contents of xml/etree/ElementTree.py will move to xml/etree/pyElementTree.py

IIRC, there is a well specified way how accelerator modules should be used
by Python modules. I recall a lengthy discussion on python-dev (or the py3k
list?) back in the old pre-3.0 days, maybe there's even a PEP?

> * xml/etree/cElementTree.py disappears.

Careful with backwards compatibility here. It's the accelerator module
(_elementtree.so, IIRC) which is to be moved behind ElementTree.py.

I don't see a compelling enough reason to break imports in existing code by
removing the cElementTree module, so we should not do that.

Stefan

History
Date	User	Action	Args
2012-02-10 15:37:17	scoder	set	recipients: + scoder, effbot, eli.bendersky, flox
2012-02-10 15:37:16	scoder	link	issue13988 messages
2012-02-10 15:37:16	scoder	create