-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Remove pytest 8 deprecations #11757
Remove pytest 8 deprecations #11757
Conversation
174a838
to
175ea47
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work!
Forgot we had so many pending deprecations...
src/_pytest/hookspec.py
Outdated
equivalent of the ``path`` parameter. | ||
|
||
.. versionchanged:: 8.0.0 | ||
The ``path`` parameter has been deprecated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually it was removed, not deprecated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was it though? It worked in 8.0 but does not work in 8.1 🤷
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as per deprecation policy, the major release tirggers errors, the next minor version removes the code
the key issue here that we missed a case where warnings don't error
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@RonnyPfannschmidt I get it. What is confusing to me is why the docs says that it was removed in 8.0 rather than that it was removed in 8.1:
From a user's point of view it would be ideal to see "deprecated in 8.0, removed in 8.1", otherwise I see that it worked in 8.0 but does not work in 8.1 and I am just confused.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the bug here is that it should have failed in 8.x, but due to a warning miss-config it did in fact not fail
the deprecation did happen - see #12068
i vaguely recall the deprecation happened later in the 7.x series as to avoid having dozens of separate deprecation events
175ea47
to
1ba0745
Compare
Per our deprecation policy, the 8.0.0 merely changes deprecation warnings to deprecation errors (which can still be ignored), with the actual removals in 8.1.0. Since main is now for 8.1, this is the time to do it.