Execute or postpone most deprecation-removals scheduled for 2.26 #21926
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
huonw
force-pushed
the
huonw/2.26-removals
branch
from
3146827 to
7486e0b
Compare
huonw
force-pushed
the
huonw/2.26-removals
branch
from
7486e0b to
2cf5200
Compare
huonw
changed the title
benjyw
approved these changes
Feb 6, 2025
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.
We're starting the 2.26.x release series so the deprecations that were scheduled for removal can be removed. This PR does handles of them.
I've postponed a few, since they were only relatively recently deprecated and require very minimal code on our side, so we can be a little more generous to any users. (e.g. the
[GLOBAL].native_options_validationand[ruff]options are unused, so it's just some option definitions that can hang around to be deleted later.)There's an extra deprecation ready for removal in the Python FaaS code, which is done in #21928 instead, because it's more fiddly/extensive.