diff options
author | Bruno Oliveira <nicoddemus@gmail.com> | 2020-07-22 21:36:51 -0300 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-07-22 21:36:51 -0300 |
commit | 7ec6401ffabf79d52938ece5b8ff566a8b9c260e (patch) | |
tree | 6b34b476b5249750c8dd893b99f64eedf8345621 /changelog | |
parent | a9799f0b35fe8fcc88ebd19b007cd2c6ac6b2a4f (diff) | |
download | pytest-7ec6401ffabf79d52938ece5b8ff566a8b9c260e.tar.gz |
Change pytest deprecation warnings into errors for 6.0 release (#7362)
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
Diffstat (limited to 'changelog')
-rw-r--r-- | changelog/5584.breaking.rst | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/changelog/5584.breaking.rst b/changelog/5584.breaking.rst new file mode 100644 index 000000000..990d04cb1 --- /dev/null +++ b/changelog/5584.breaking.rst @@ -0,0 +1,23 @@ +**PytestDeprecationWarning are now errors by default.** + +Following our plan to remove deprecated features with as little disruption as +possible, all warnings of type ``PytestDeprecationWarning`` now generate errors +instead of warning messages. + +**The affected features will be effectively removed in pytest 6.1**, so please consult the +`Deprecations and Removals <https://docs.pytest.org/en/latest/deprecations.html>`__ +section in the docs for directions on how to update existing code. + +In the pytest ``6.0.X`` series, it is possible to change the errors back into warnings as a +stopgap measure by adding this to your ``pytest.ini`` file: + +.. code-block:: ini + + [pytest] + filterwarnings = + ignore::pytest.PytestDeprecationWarning + +But this will stop working when pytest ``6.1`` is released. + +**If you have concerns** about the removal of a specific feature, please add a +comment to `#5584 <https://github.com/pytest-dev/pytest/issues/5584>`__. |