Skip to content

Conversation

rhshadrach
Copy link
Member

@rhshadrach rhshadrach commented Aug 21, 2025

  • closes #xxxx (Replace xxxx with the GitHub issue number)
  • Tests added and passed if fixing a bug or adding a new feature
  • All code checks passed.
  • Added type annotations to new arguments/methods/functions.
  • Added an entry in the latest doc/source/whatsnew/vX.X.X.rst file if fixing a bug or adding a new feature.

Replaces all appropriate FutureWarnings and DeprecationWarnings with Pandas4Warnings. For those that are to be enforced in 3.0, I added # TODO: Enforce .... I plan to introduce linting rules on FutureWarning/DeprecationWarning next.

@@ -930,6 +930,7 @@ def _logical_method(self, other, op) -> Self:
and isinstance(other, np.ndarray)
and other.dtype == bool
):
# TODO: Enforce in 3.0 (#60234)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if this one should already be enforced?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yea, agreed. I've changed this to Pandas4Warning and moved the deprecation from the 3.0 issue to the 4.0 issue.

@rhshadrach rhshadrach marked this pull request as ready for review August 23, 2025 12:30
@rhshadrach rhshadrach requested a review from mroeschke August 23, 2025 19:51
@mroeschke mroeschke added the Warnings Warnings that appear or should be added to pandas label Aug 25, 2025
@mroeschke mroeschke added this to the 3.0 milestone Aug 25, 2025
@mroeschke mroeschke merged commit 594889e into pandas-dev:main Aug 25, 2025
42 checks passed
@mroeschke
Copy link
Member

Thanks @rhshadrach

@rhshadrach rhshadrach deleted the future_warning_comments branch August 25, 2025 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Warnings Warnings that appear or should be added to pandas
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants