Skip to content

CLN remove dataframe api consortium entrypoint #57482

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 19, 2024

Conversation

MarcoGorelli
Copy link
Member

@MarcoGorelli MarcoGorelli commented Feb 18, 2024

Discussed privately

In short:

  • I'm no longer involved in the project
  • nobody in pandas has much interest in leading the effort
  • pandas devs are already carrying out enough (mostly unpaid) maintenance, let's not add to it

The Consortium is more than welcome to work on this, but outside of pandas

@MarcoGorelli MarcoGorelli marked this pull request as ready for review February 19, 2024 12:33
Copy link
Member

@jbrockmendel jbrockmendel left a comment

Choose a reason for hiding this comment

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

LGTM

@MarcoGorelli MarcoGorelli added this to the 3.0 milestone Feb 19, 2024
@MarcoGorelli MarcoGorelli merged commit d279726 into pandas-dev:main Feb 19, 2024
pmhatre1 pushed a commit to pmhatre1/pandas-pmhatre1 that referenced this pull request May 7, 2024
@anmyachev
Copy link
Contributor

Just curious why you didn't update the What's New section to match the way it was done when adding the entrypoint: 809f371#diff-cc8593fd6d3036f46dbd73bcd245aef9a5e737cd22ca67e9567e686872bf093e. It took me a while to figure out where it was deleted.

@rgommers are you aware of this change?

@MarcoGorelli
Copy link
Member Author

Hey Anatoly,

I can't remember exactly, I probably just forgot

@rgommers
Copy link
Contributor

@rgommers are you aware of this change?

I don't think I was, thanks for pointing it out.

This change was breaking it looks like (or you wouldn't have noticed in Modin I think), and the maintenance burden was minimal (xref gh-54383 comments), so I wouldn't have done it this way. But ultimately decisions like this are up to the maintainers alone, so it is what it is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants