Remove deprecations preparing for v5 - #969
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #969 +/- ##
==========================================
Coverage 100.00% 100.00%
==========================================
Files 28 27 -1
Lines 9388 8729 -659
==========================================
- Hits 9388 8729 -659 ☔ View full report in Codecov by Harness. |
|
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
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.

What does this PR do?
Removes all features deprecated during v4 and makes the announced v5 behaviors the default. The
_deprecatedmodule and its test file are deleted, and the documentation drops the notes that described the transitional behaviors.What was removed or changed, and how to update code, is already in the
v5.0.0section of the changelog and in the migrate to v5 guide, so it is not repeated here.Not covered there, since it is not user facing: internal code paths that the removals made unreachable are deleted as well, e.g. the list handling in
replace_unsetandexpand_dict, only needed for behaviors that no longer exist.Before submitting