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

Remove pytest 8 deprecations #11757

Merged
merged 12 commits into from
Jan 3, 2024
Merged

Conversation

bluetech
Copy link
Member

@bluetech bluetech commented Jan 2, 2024

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.

@bluetech bluetech force-pushed the rm-removed-in-8 branch 2 times, most recently from 174a838 to 175ea47 Compare January 2, 2024 11:30
Copy link
Member

@nicoddemus nicoddemus left a 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...

equivalent of the ``path`` parameter.

.. versionchanged:: 8.0.0
The ``path`` parameter has been deprecated.
Copy link
Member

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.

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 🤷

Copy link
Member

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

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:

image

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.

Copy link
Member

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

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.

4 participants