Skip to content
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

Introduce warning subclasses for each type of warning we emit #5177

Closed
nicoddemus opened this issue Apr 27, 2019 · 0 comments

Comments

Projects
None yet
1 participant
@nicoddemus
Copy link
Member

commented Apr 27, 2019

As we did with UnknownMarkWarning in #4935, we should create various subclasses for all the types of warnings we emit: not collecting classes with __init__, unknown markers, etc.

@nicoddemus nicoddemus added this to the 4.5 milestone Apr 27, 2019

nicoddemus added a commit to nicoddemus/pytest that referenced this issue Apr 28, 2019

nicoddemus added a commit to nicoddemus/pytest that referenced this issue Apr 28, 2019

nicoddemus added a commit to nicoddemus/pytest that referenced this issue Apr 28, 2019

@nicoddemus nicoddemus closed this Apr 29, 2019

miketheman added a commit to miketheman/pytest-black that referenced this issue May 15, 2019

fix: address PytestUnknownMarkWarning
As of pytest 4.5.0, a new warning is raised when the plugin doesn't
register its markers. See pytest-dev/pytest#5177

The docs recommend registering custom markers:
https://docs.pytest.org/en/latest/writing_plugins.html#registering-markers

Signed-off-by: Mike Fiedler <miketheman@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.