Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[prerelease] pytest.warns() doesn't seem to work properly for coverage.py

See original GitHub issue

From @nedbat via Twitter:

This message could be better, because removing None doesn’t work now:
PytestRemovedIn8Warning: Passing None to catch any warning has been deprecated, pass no arguments instead:
  Replace pytest.warns(None) by simply pytest.warns().
When I remove None and run with pytest 7, I get failures:

No idea off-hand what’s going on there, as that seems exactly what we did in #8677 too.

cc @Zac-HD @olgarithms

Issue Analytics

State:
Created 2 years ago
Comments:10 (10 by maintainers)

Top GitHub Comments

1reaction

nedbatcommented, Dec 8, 2021

We never actually had that though! Before, it would pass for any or no warnings, which would be useless if it wasn’t also misleading.

I see! I was definitely misunderstanding it then. If a new context manager isn’t available in 7.0, I can write one of my own for my test suite. Thanks.

1reaction

The-Compilercommented, Dec 7, 2021

Ah, makes sense! I guess in @nedbat’s scenario indeed the warning is “optional”. So I suppose we can close this one as a duplicate then?