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 ezio.melotti
Recipients Arfrever, effbot, eli.bendersky, eric.araujo, ezio.melotti, flox, pjenvey, python-dev, scoder, tshepang
Date 2012-02-16.13:04:25
SpamBayes Score 3.0844349e-06
Marked as misclassified No
Message-id <>
I'm still not sure that's the best option.  Without deprecation people will keep using cElementTree and we will have to keep it around forever (or at least until Python4 and then have a 3to4 to fix the import).
This might be fine, but as a developer I would still like Python to tell me "You can just import ElementTree now, there's no need to use cElementTree".  Maybe the deprecation can be added to 3.4?

P.S. I'm fine with keeping it around for several more versions, but if we eventually have to remove it, we would still have to warn the users beforehand.  The more we wait, the more users will be still using cElementTree by the time we will actually remove it.
Date User Action Args
2012-02-16 13:04:26ezio.melottisetrecipients: + ezio.melotti, effbot, scoder, pjenvey, eric.araujo, Arfrever, eli.bendersky, flox, tshepang, python-dev
2012-02-16 13:04:26ezio.melottisetmessageid: <>
2012-02-16 13:04:25ezio.melottilinkissue13988 messages
2012-02-16 13:04:25ezio.melotticreate