This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author scoder
Recipients effbot, eli.bendersky, flox, scoder
Date 2012-02-10.15:55:22
SpamBayes Score 9.682827e-11
Marked as misclassified No
Message-id <>
In-reply-to <>
Eli Bendersky, 10.02.2012 16:43:
>>> 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.
> Agreed. Perhaps it should just be deprecated?

Given that its mere existence is currently almost undocumented (except for
one tiny sentence in the docs), I vote for clearly documenting it as
deprecated, yes, with a mention to the fact that it's automatically used by
xml.etree.ElementTree starting with 3.3.

I wouldn't want to see more than that done, though, specifically not a
visible warning when it's being imported. There's far too much code out
there that uses it in previous Python versions. Such a warning would strike
even if it's only being imported conditionally with a try-except, which is
the most common way of doing it. So it would hit most users and require an
awful lot of code to be touched to fix it, for basically zero benefit.

Date User Action Args
2012-02-10 15:55:23scodersetrecipients: + scoder, effbot, eli.bendersky, flox
2012-02-10 15:55:22scoderlinkissue13988 messages
2012-02-10 15:55:22scodercreate