On Sat, Mar 23, 2019 at 2:26 AM Brett Cannon <br...@python.org> wrote: > > > We can't do that as it will break code. Think of code which is having > warnings raise exceptions and that are purposefully catching > PendingDeprecationWarning but not DeprecationWarning; this change would break > that. These classes are part of the public API of the warnings module and so > we shouldn't change semantics like that for people who have a specific use > for those two different classes regardless of how the stdlib may choose to > use them. >
Didn't we already do it? socket.error was independent error class. It became alias of OSError from Python 3.3. There might be some small troubles. But it was small enough for Python minor versions, I think. -- Inada Naoki <songofaca...@gmail.com> _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
