Andrei Kulakov <andrei....@gmail.com> added the comment:
Steve: it seems to me that the goal of normal deprecation process is, given that a functionality is available and documented, prepare to find a replacement for it by some future version. In this case it's documented not to be available and doesn't work so this should perhaps fall under fixing a bug? It's true that this is backwards incompatible for the reason you pointed out (and I missed), but I think breaking compatibility is ok in new versions for bug fixes? (as long as it's added to "what's new", which I haven't done yet). If I'm wrong about this, I'll go ahead and make another PR for deprecation and close this one.. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33140> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
