PEP 608: DeprecatedWarning => DeprecationWarning
This commit is contained in:
parent
4b664da442
commit
77d093d3d1
10
pep-0608.rst
10
pep-0608.rst
|
@ -49,16 +49,16 @@ in their CI, too many projects of the top 50 PyPI projects are only
|
|||
compatible with the new Python a few weeks, or even months, after the
|
||||
final Python release.
|
||||
|
||||
DeprecatedWarning is being ignored
|
||||
----------------------------------
|
||||
DeprecationWarning is being ignored
|
||||
-----------------------------------
|
||||
|
||||
Python has well defined process to deprecate features. A
|
||||
DeprecatedWarning must be emitted during at least one Python release,
|
||||
DeprecationWarning must be emitted during at least one Python release,
|
||||
before a feature can be removed.
|
||||
|
||||
In practice, DeprecatedWarning warnings are ignored for years in major
|
||||
In practice, DeprecationWarning warnings are ignored for years in major
|
||||
Python projects. Usually, maintainers explain that there are too many
|
||||
warnings and so they simply ignore warnings. Moreover, DeprecatedWarning
|
||||
warnings and so they simply ignore warnings. Moreover, DeprecationWarning
|
||||
is silent by default (except in the ``__main__`` module: `PEP 565
|
||||
<https://www.python.org/dev/peps/pep-0565/>`_).
|
||||
|
||||
|
|
Loading…
Reference in New Issue