On 11. 05. 21 11:08, Inada Naoki wrote:
On Tue, May 11, 2021 at 5:30 PM Petr Viktorin <encu...@gmail.com> wrote:
Test tools should treat DeprecationWarning as error by default [0][1].
So even if end users don't really see it, I don't consider it "hidden".
*should* is not *do*. For example, nosetests don't show DeprecationWarning.
And there are many scripts without tests.
So it is hidden for some people.
Sadly, there's not much we can do for users of nose. Nose itself is only
tested with Python 3.5 and below.
I'm aware that there are scripts without tests. But maybe letting them
suddenly break is the right balance between letting people know and
annyoing everyone with unactionable warnings.
If DeprecationWarning is not enough, then we should be having a wider
discussion, and PEP 387 should change. This particular issue should not
be an exception to the process.
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/FWFZWMSWWV5KNM3LSU5NQCSDO7YLUARU/
Code of Conduct: http://python.org/psf/codeofconduct/