Raymond Hettinger <rhettin...@users.sourceforge.net> added the comment:
There is *no* reason to downgrade the warning. We can leave it as deprecated in 3.1 and remove it in 3.3 if we want. A PendingDeprecationWarning is just a plain bad idea, it doesn't actually warn the users. We introduced that construct in Python 2.3 to be used *rarely* for deeply entrenched things like string exceptions that would be eventually removed. For the most part, everything else gets deprecated directly. Also, remember that this construct is not being deprecated just because it is duplicative; it is being deprecated because it is a bug factory when used as advertised -- it is a harmful construct -- it *needs* a warning. Someone like Hagan, using it for a corner case, can easily put a copy and paste version in their own code and use it forever. There are likely very few such users now (but there will be more if we fail to provide a real warning). ---------- nosy: +rhettinger _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6288> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
