How to suppress py.test internal deprecation warnings

Question

Is there a way to suppress the pytest's internal deprecation warnings?

Context: I'm looking to evaluate the difficulty of porting a test suite from nose to pytest. The suite is fairly large and heavily uses nose-style yield based test generators.

I'd like to first make sure the existing tests pass with pytest, and then maybe change test generators to parameterized.

Just running $ pytest path-to-test-folder with pytest 3.0.4 is completely dominated by pages and pages of

WC1 ~repos/numpy/numpy/lib/tests/test_twodim_base.py yield tests are deprecated, and scheduled to be removed in pytest 4.0

Is there a way of turning these warnings off?

rabyj · Accepted Answer · 2023-07-07 16:46:59Z

239

I think you do not want to hide all warnings, but just the ones that are not relevant. And in this case, deprectation warnings from imported python modules.

Having a read on pytest documentation about Warnings Capture:

Both -W command-line option and filterwarnings ini option are based on Python’s own -W option and warnings.simplefilter, so please refer to those sections in the Python documentation for other examples and advanced usage.

So you can filter warnings with python's -W option!

It seems that pytest completely removes filters, because it shows all those DeprecationWarning when running, and Python's documentation about Default Warning Filters clearly says:

In regular release builds, the default warning filter has the following entries (in order of precedence):
default::DeprecationWarning:__main__
ignore::DeprecationWarning
ignore::PendingDeprecationWarning
ignore::ImportWarning
ignore::ResourceWarning

So in your case, if you want let say to filter types of warning you want to ignore, such as those DeprecationWarning, just run the pytest command with -W option :

$ pytest path-to-test-folder -W ignore::DeprecationWarning

EDIT: From colini's comment, it is possible to filter by module. Example to ignore deprecation warnings from all sqlalchemy :

ignore::DeprecationWarning:sqlalchemy.*:

You can then list your installed modules that creates too much noise in the output of pytest

EDIT2: For more precise control, the Python documentation about Describing Warning Filters states that the general way to write such warning filters is:

action:message:category:module:line

Use with file rather than in command line:

You may prefer list those filters in pytest.ini file :

[pytest]
filterwarnings =
    ignore::DeprecationWarning

edited Jul 7, 2023 at 16:46

rabyj

701 silver badge7 bronze badges

answered Nov 9, 2018 at 1:40

SivolcC

3,6783 gold badges17 silver badges32 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

colini Over a year ago

To filter on the module you use a regex. Example to ignore deprecation warnings from all sqlalchemy modules:ignore::DeprecationWarning:sqlalchemy.*:

WhiteHotLoveTiger Over a year ago

@colini that failed for me as an argument to the -W flag, but it worked for me in my pytest.ini file.

Matt Sanders Over a year ago

In pytest 6.1 the trailing regex isn't working for me, but you can insert a regex in the middle to match against the beginning of the warning message. ignore:.*U.*mode is deprecated:DeprecationWarning ignores all warnings of type DeprecationWarning where the start of the message matches the regular expression ".*U.*mode is deprecated". more info

Felix Benning Over a year ago

@WhiteHotLoveTiger same with ignore::DeprecationWarning:tensorflow[.*] - only works for the configuration files, filed a bug report: github.com/pytest-dev/pytest/issues/8751

bluenote10 Over a year ago

@MattSanders I also noticed that I cannot get module regex matching to work. Did you check if it is only a pytest issue? In my case it turned out to be even more fundamental: Even with a plain PYTHONWARNINGS="..." python -c "...", module matching doesn't seem to work as the documentation describes it. Post as a follow-up question.

The Compiler · Accepted Answer · 2016-11-21 16:02:21Z

188

From pytest --help:

--disable-pytest-warnings
                      disable warnings summary, overrides -r w flag

answered Nov 21, 2016 at 16:02

The Compiler

12.2k4 gold badges45 silver badges57 bronze badges

2 Comments

David Pärsson Over a year ago

As the help text says, this will only omit the textual summary. The result will still be yellow and show that there are warnings.

vy32 Over a year ago

Better to put in the pytest.ini file, as shown below.

Blaise · Accepted Answer · 2019-10-21 07:41:21Z

142

pytest -p no:warnings, or add the following to your pytest.ini or tox.ini:

[pytest]
addopts = -p no:warnings

The result will be green without any indication of warnings. See documentation at https://docs.pytest.org/en/latest/warnings.html#disabling-warnings-summary.

This can be a valid use case for a test suite where you want clean output.

Be aware that always hiding all warnings may cause you to miss important warnings. If you want to hide only specific warnings, look at Cloc's answer.

edited Oct 21, 2019 at 7:41

answered Jun 12, 2018 at 15:47

Blaise

13.6k9 gold badges79 silver badges103 bronze badges

2 Comments

Peter M. - stands for Monica Over a year ago

addopts = -p no:warnings is REALLY BAD idea, and CloC solution is much saner, but I had to use yours when ignore::InsecureRequestWarning was not recognized, so you get +1 too

Neowizard Over a year ago

Disabling all warnings persistently (i.e. using pytest.ini) is almost never a good idea. Disabling just Deprecation warning (and by module) as CloC describes is the right way to do this.

pk786 · Accepted Answer · 2020-02-20 18:11:55Z

27

In the pytest.ini file you can add:

[pytest]
addopts = -p no:warnings

OR passing below line in the command-line. This might be useful if your test suites handle warnings using an external system.

-p no:warnings

OR if you only want to hide some specific deprecated warning, add below statement in you pytest.ini file

[pytest]
filterwarnings =
    ignore:.*U.*mode is deprecated:DeprecationWarning

This will ignore all warnings of type DeprecationWarning where the start of the message matches the regular expression ".*U.*mode is deprecated".

OR Although not recommended, you can use the

--disable-warnings

command-line option to suppress the warning summary entirely from the test run output.

answered Feb 20, 2020 at 18:11

pk786

2,4803 gold badges25 silver badges25 bronze badges

Comments

Polv · Accepted Answer · 2019-01-19 07:42:44Z

17

I don't want to hide all warning, so I put this in pytest.ini

[pytest]
filterwarnings =
    ignore::DeprecationWarning

answered Jan 19, 2019 at 7:42

Polv

2,2461 gold badge25 silver badges36 bronze badges

Comments

rabyj · Accepted Answer · 2023-07-07 00:02:40Z

12

Here is a link for how to suppress warnings if you are using pyproject.toml file as configuration.

[tool.pytest.ini_options]
testpaths = ["./tests/unit"]
filterwarnings = ["ignore:::.*third_party_package.module:123", "ignore:::.*another_module*"]

123 in this case is a line number to be suppressed

For more information on the general way to write warning filters, see the python official doc at "The Warnings Filter" and "Describing Warning Filters". In short, Individual warnings filters are specified as a sequence of fields separated by colons: action:message:category:module:line

edited Jul 7, 2023 at 0:02

rabyj

701 silver badge7 bronze badges

answered Oct 18, 2021 at 20:49

Vlad Bezden

90.8k27 gold badges261 silver badges190 bronze badges

1 Comment

spencerlou Over a year ago

filterwarnings = ["ignore::DeprecationWarning"] to ignore all deprecated warnings for this situation

colidyre · Accepted Answer · 2023-02-18 10:27:07Z

5

I want to add that it is also possible to filter the warnings in a fine-granular way by understanding the parsing mechanism which is well explained in the warnings section of the python documentation.

Individual warnings filters are specified as a sequence of fields separated by colons: action:message:category:module:line

This allows you to e.g. disable a specific warning with a specific message for a specific module only. For me, it was using pytest-freezegun, but not showing the annoying DeprecationWarning for using distutils Version classes.

Without applying the described filter from below the relevant output part from pytest runner is:

.venv/lib/python3.11/site-packages/pytest_freezegun.py:17: 34 warnings
tests/test_folder1/test_1.py: 10 warnings
tests/test_folder1/test_2.py: 4 warnings
  /my/project/path/.venv/lib/python3.11/site-packages/pytest_freezegun.py:17: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
    if LooseVersion(pytest.__version__) < LooseVersion('3.6.0'):

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html

And with this setting in pyproject.toml, the DeprecationWarning for not using packaging.version is completely gone, but only for pytest-freezegun (because I do not want to deactivate all deprecation warnings for the whole project):

[tool.pytest.ini_options]
testpaths = ["./tests"]
filterwarnings = ["ignore:.*distutils Version classes.*packaging.version:DeprecationWarning:pytest_freezegun"]

In detail:

ignore:.*distutils Version classes.*packaging.version:DeprecationWarning:pytest_freezegun
^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^
action       message (regular expression)                  category           module

Note: I do not want to include the line number, because library code could be changed without fixing the DeprecationWarning.

(The possibility of filtering has also been mentioned in a comment, but I wanted to elaborate a little more.)

answered Feb 18, 2023 at 10:27

colidyre

4,88512 gold badges46 silver badges65 bronze badges

2 Comments

loco.loop Over a year ago

Nice. However, if you wanted to correct the freezegun warning, how would you do it?

colidyre Over a year ago

@loco.loop This warning is coming from the freezegun package. So you can fix it there or write an issue at github. I have not looked into it. Maybe it is already fixed or there is already an issue for it. From inside your project, you should never touch library code (there might be rare exceptional cases, but this is generally a really bad idea).

Jubin Ben · Accepted Answer · 2023-03-29 04:03:46Z

2

If you'd like to ignore all the warnings from the pytest file itself. Just add the following in your pytest file:

import warnings; warnings.filterwarnings("ignore")

answered Mar 29, 2023 at 4:03

Jubin Ben

612 bronze badges

Comments

Richard de Wit · Accepted Answer · 2021-11-25 07:15:35Z

1

If you use a setup.cfg file, put this in:

[tool:pytest]
addopts = -p no:warnings

You need tool:pytest instead of just pytest, but it will tell you:

Failed: [pytest] section in setup.cfg files is no longer supported, change to [tool:pytest] instead.

answered Nov 25, 2021 at 7:15

Richard de Wit

7,5207 gold badges48 silver badges59 bronze badges

Comments

jamyla · Accepted Answer · 2024-04-01 08:26:06Z

1

${PYTHON} -m pytest -W ignore::DeprecationWarning

DeprecationWarning Will help remove the imports decrecations warning coming up when we run pytest .

This can be used in makefile.py to ignore the warnings

edited Apr 1, 2024 at 8:26

answered Feb 27, 2023 at 6:17

jamyla

453 bronze badges

1 Comment

Tyler2P Over a year ago

Your answer could be improved by adding more information on what the code does and how it helps the OP.

collinsmarra · Accepted Answer · 2024-01-11 16:53:34Z

0

when working with multiple warnings,

python -m pytest -W ignore::DeprecationWarning -W ignore::ImportWarning

answered Jan 11, 2024 at 16:53

collinsmarra

1782 silver badges10 bronze badges

Comments

abdoulsn · Accepted Answer · 2025-02-13 16:31:33Z

0

When you want to suppress multiples warning:

[pytest] // or [tool:pytest]
filterwarnings =
    ignore::DeprecationWarning
    ignore::PendingDeprecationWarning
    ignore::UserWarning
    ignore::RuntimeWarning

answered Feb 13, 2025 at 16:31

abdoulsn

1,2013 gold badges22 silver badges39 bronze badges

Comments

fferses · Accepted Answer · 2025-03-11 09:56:09Z

0

If you used pyproject.toml file

You may prefer list those filters in pyproject.toml file :

[tool.pytest.ini_options]
filterwarnings = [
    "ignore::DeprecationWarning"
]

answered Mar 11, 2025 at 9:56

fferses

1

Comments

Stephen Arnold · Accepted Answer · 2025-05-26 02:05:50Z

0

I tried several (TOML) variants of the above answers, but the one that finally worked for me was:

[tool.pytest.ini_options]
...
filterwarnings = ["ignore:currentThread:DeprecationWarning",]

answered May 26, 2025 at 2:05

Stephen Arnold

491 silver badge3 bronze badges

Collectives™ on Stack Overflow

How to suppress py.test internal deprecation warnings

14 Answers 14

5 Comments

2 Comments

2 Comments

Comments

Comments

1 Comment

2 Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

14 Answers 14

5 Comments

2 Comments

2 Comments

Comments

Comments

1 Comment

2 Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related