On Fri, Mar 22, 2019 at 5:06 PM Victor Stinner <vstin...@redhat.com> wrote: > > Le ven. 22 mars 2019 à 08:54, Inada Naoki <songofaca...@gmail.com> a écrit : > > Yes. It will be removed at some point, but not in near future. > > > > But when when backward compatibility can be kept by alias, > > we can be very lazy about removing it. > > Honestly, I don't see the point of removing PendingDeprecationWarning > anytime soon. Practicality beats purity.
I totally agree. > Removing PendingDeprecationWarning doesn't bring any value to anyone. > "PendingDeprecationWarning = DeprecationWarning" costs nothing in term > of maintenance. > > If you care, I would suggest to invest time in static analyzers like > pycodestyle, pylint, pyflakes, etc. Emit a warning with a low > priority, and let users make their own choices. Agree too. > > > We have `socket.error` for long time. > > And it's perfectly fine, no? > Yes. Waiting 10+ years to remove aliases is fine. -- 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
