Le 21/04/2021 à 13:34, Victor Stinner a écrit :
On Wed, Apr 21, 2021 at 1:24 PM M.-A. Lemburg <m...@egenix.com> wrote:
Isn't that an educational problem ? Adjusting reporting of
warnings isn't all that hard:
A common practical problem is a project CI which pulls the most recent
verisons of 3rd party dependencies and suddenly break if a new
deprecation warning is raised by such project.
If a warning breaks CI, does it mean that the CI set non-default
warnings flags (i.e. turn them into errors)? But we're talking about the
default flags.
As a concrete data point, some packages in the scientific ecosystem have
decided to use FutureWarning instead of DeprecationWarning, precisely
because DeprecationWarnings are silent by default and users never see
them. This is an ecosystem where users are often non-professional
developers, and the fact that DeprecationWarning is hidden by default
hits them hard, because they are not aware that they need to change
something.
Regards
Antoine.
_______________________________________________
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https://mail.python.org/archives/list/python-committers@python.org/message/FLYC2X3MWAHWVDURC5ZP4THE4NJPRGMF/
Code of Conduct: https://www.python.org/psf/codeofconduct/
