Skip to content

Conversation

@jorisvandenbossche
Copy link
Member

Small follow-up on #60357, keeping the existing names for the objects that subclasses might check for in custom logic in __finalize__.

We can deprecate accessing those additional names later, but that is not critical for 3.0

@jorisvandenbossche jorisvandenbossche added this to the 3.0 milestone Dec 17, 2025
@jorisvandenbossche jorisvandenbossche added the Subclassing Subclassing pandas objects label Dec 17, 2025
Copy link
Member

@mroeschke mroeschke left a comment

Choose a reason for hiding this comment

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

Did you discover this in geopandas?

@jorisvandenbossche
Copy link
Member Author

Yes, and we have a fix for it as well (to be released before the final 3.0 release), but it seems easy to also provide compat for those who would test the latest pandas with one earlier release of geopandas (instead of giving some cryptic error)

@mroeschke mroeschke merged commit 080b6b5 into pandas-dev:main Dec 17, 2025
74 of 77 checks passed
@mroeschke
Copy link
Member

Thanks @jorisvandenbossche

@jorisvandenbossche jorisvandenbossche deleted the finalize-compat branch December 17, 2025 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Subclassing Subclassing pandas objects

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants