Larry Hastings added the comment: This isn't a release blocker. And it's not really viable to remove it.
Since it's been in several releases, I suspect our only option is to throw a deprecation warning. And, since deprecations aren't turned on by default, maybe the best thing would be to also document it (!) as being deprecated (!!). Even though rc1 is already tagged and in the process of being released, I will accept a patch with the above suggested change for Python 3.4. If you want to do something else talk to me first. ---------- priority: release blocker -> normal _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue20572> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
