CLN: Lint for usage of Deprecation/FutureWarning #62178
Open
+166
−43
Conversation
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
rhshadrach
added
CI
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.
doc/source/whatsnew/vX.X.X.rstfile if fixing a bug or adding a new feature.Adds linting to enforce PDEP-17, namely that contributors do not raise
PendingDeprecationWarning,DeprecationWarning, norFutureWarningbut rather the pandas subclasses of these.Also adds an escape hatch for this: add
# pdlint: ignore[warning_class]to any line which you want to override the linting. Useful right now for some tests as well as deprecations that are still to be enforced in 3.0. For a few a of the warnings, they were meant to bePandas4Warningsas they were only introduced in PRs tagged3.0.