Update deprecation markers (3.1 -> 3.0.1) - #3422
Merged
Merged
Conversation
deruyter92
force-pushed
the
jaap/update-deprecation-markers
branch
from
July 20, 2026 20:34
ba50483 to
add1845
Compare
MMathisLab
self-requested a review
July 21, 2026 02:14
MMathisLab
approved these changes
Jul 21, 2026
deruyter92
force-pushed
the
jaap/pathlib-hardening
branch
from
July 21, 2026 06:48
92cdc1a to
0a9bbbc
Compare
deruyter92
force-pushed
the
jaap/update-deprecation-markers
branch
from
July 21, 2026 06:49
add1845 to
30c469d
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Several deprecation markers now are introduced for the new release (e.g.
@deprecatedor@renamed_parameter) that emit a message that a function or parameter is deprecated "since version 3.1". As we are releasing version 3.0.1 (minor release), this should be adapted accordingly.