8000 Roadmap for Dataframe API · Issue #319 · data-apis/dataframe-api · GitHub
[go: up one dir, main page]
Skip to content

Roadmap for Dataframe API #319

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.

Sign up for GitHub

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

Jump to bottom
Closed
MarcoGorelli opened this issue Nov 14, 2023 · 1 comment
Closed

Roadmap for Dataframe API #319

MarcoGorelli opened this issue Nov 14, 2023 · 1 comment
Labels
API design

Comments

@MarcoGorelli
Copy link
Contributor
MarcoGorelli commented Nov 14, 2023 •
edited
Loading

Let's try to get a roadmap together. I'm a little worried that at the current pace it'll take another year until we can publish a non-beta spec. That's too long. So let's zoom out and think about what we'd like to achieve, and if this can help re-prioritise.

Here's some milestones I'd like to aim for:

  • by the end of the year: merge (or achieve some other resolution) on the following topics:
    • ✅ have a Scalar class
    • ✅ cross-dataframe column comparisons
  • by February 2024
    • tag the first non-beta version
  • by April 2024, make sure the spec and dataframe-api-compat are complete enough that it's possible to rewrite the majority of some dataframe-consuming library using the standard
  • by November 2024, have production-ready implementations of the standard for all libraries involved

If we want to achieve the above, then we need to turn things around. In particular, this may mean not getting lost in details - in particular, I suggest punting on:

  • propagation of persistedness (including whether this should be done at all)
  • whether Scalar.__bool__ is allowed to raise

and leaving these implementation-specific for now. If we do manage to turn things around and make good progress on the roadmap above, we could (and probably should!) bring these up again
@MarcoGorelli MarcoGorelli mentioned this issue Nov 17, 2023
Closed
@MarcoGorelli
Copy link
Contributor Author

by February 2024. tag the first non-beta version

Moving this forwards indefinitely until #346 is resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
API design
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MarcoGorelli
0