Expire deprecations in lines and patches #22486
Merged
Conversation
This file contains 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
oscargus
force-pushed
the
patchdeprecations
branch
2 times, most recently
from
7e2409a
to
a8045ba
Compare
QuLogic
reviewed
Feb 17, 2022
oscargus
force-pushed
the
patchdeprecations
branch
from
a8045ba
to
4b5a8b7
Compare
dstansby
approved these changes
Feb 18, 2022
QuLogic
reviewed
Feb 18, 2022
oscargus
force-pushed
the
patchdeprecations
branch
from
4b5a8b7
to
8466d11
Compare
timhoffm
approved these changes
Feb 20, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Summary
Expired deprecations in lines and patches.
There are some more deprecations in patches, but I didn't really understand what should be kept and not.
PR Checklist
Tests and Styling
pytestpasses).flake8-docstringsand runflake8 --docstring-convention=all).Documentation
doc/users/next_whats_new/(follow instructions in README.rst there).doc/api/next_api_changes/(follow instructions in README.rst there).