Skip to content

warn specific classes #361

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Jul 25, 2021

Conversation

graingert
Copy link
Member

No description provided.

@graingert graingert requested a review from nicoddemus November 19, 2019 08:55
@graingert graingert force-pushed the warn-specific-warn-classes branch 4 times, most recently from fe580ae to 56b0cfb Compare November 19, 2019 09:13
@ionelmc ionelmc force-pushed the warn-specific-warn-classes branch from 56b0cfb to 1734d2d Compare January 12, 2020 19:21
@ionelmc
Copy link
Member

ionelmc commented Jan 12, 2020

So I took the liberty of rebasing - master has the CI fixed now.

@graingert graingert requested a review from ionelmc July 20, 2021 15:52
@ionelmc
Copy link
Member

ionelmc commented Jul 25, 2021

Seems simple enough, tests pass, I guess we'll see if we break weird warning filters on the next release.

@ionelmc ionelmc merged commit d810c65 into pytest-dev:master Jul 25, 2021
@graingert graingert deleted the warn-specific-warn-classes branch July 25, 2021 12:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants