DOC: pytest.warns() fails on zero warning#9611
Merged
bluetech merged 1 commit intopytest-dev:mainfrom Feb 8, 2022
Merged
Conversation
nicoddemus
approved these changes
Feb 5, 2022
Member
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow up of #9495 . Turns out
pytest.warns()is not a drop-in replacement for the way we usepytest.warns(None)(astropy/astropy#12823). "Any" in the doc got me to believe that it will pass even with zero warning but the test fails when there is no warning with this, so this is an attempt to improve a doc a bit more.p.s. This does not need a change log and I don't think a one word change qualify my name on authors list.