<div dir="ltr">> Currently in 3.3 the whole cElementTree module is:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
><br>
> # Deprecated alias for xml.etree.ElementTree<br>
><br>
> from xml.etree.ElementTree import *<br>
><br>
> Would it be alright to issue a DeprecationWarning if this module is<br>
> imported? Then hopefully a couple of releases after 3.3 we can just dump it.<br>
<br>
</div>What do we really gain by dumping it, though? Just add a CPython<br>
specific test that ensures:<br>
<br>
for key, value in xml.etree.ElementTree.__dict__.items():<br>
self.assertIs(getattr(xml.etree.cElementTree, key), value)<br>
<br>
and then ignore it for the next decade or so.<br>
<br></blockquote><div><br>With the deprecation warning being silent, is there much to lose, though? Cleanups help lower the clutter and mental burden on maintainers in the long run. If nothing is ever cleaned up don't we end up with PHP :-) ?<br>
<br> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Programmatic deprecation is a significant imposition on third party<br>
developers and should really be reserved for APIs that actively<br>
encourage writing broken code (e.g. contextlib.nested) or are<br>
seriously problematic for python-dev to maintain. For cleanup stuff,<br>
documented deprecation is sufficient.<br>
<br></blockquote><br>A quick search of the sources for DeprecationWarning show that it's being used much more liberally than solely for stuff that encourages writing broken code. Has there been a recent policy change with regards to what's considered deprecated?<br>
<br>Eli<br><br><br><br><br><br><br><br></div><br></div>