Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

api: plan for narwhals.stable.v2 #1656

Closed
MarcoGorelli opened this issue Dec 24, 2024 · 0 comments
Closed

api: plan for narwhals.stable.v2 #1656

MarcoGorelli opened this issue Dec 24, 2024 · 0 comments

Comments

@MarcoGorelli
Copy link
Member

I think we can aim for narwhals.stable.v2 some time in 2025

The main things I'd like to achieve are:

  • remove "interchange" level of support, and instead only have:
    • "full": must support Series and have a defined row order (pandas, polars.DataFrame, pyarrow.Table, modin.DataFrame, cudf.DataFrame)
    • "lazy": must support collect, adding/removing/subsetting columns, filtering rows. Initially, at least, row-order-dependent operations (such as nw.cum_sum) will be left out. This will include Polars.LazyFrame, DuckDBPyRelation, pyspark.DataFrame, ibis.Table, dask.DataFrame
  • make the breaking changes listed in breaking changes

Candidate changes:

  • rework from_native. It will get simpler once we remove interchange-level things, but it's still fairly complicated. Not sure how much I like it to be completely honest

Usage of narwhals.stable.v1 should remain unaffected

@narwhals-dev narwhals-dev locked and limited conversation to collaborators Dec 24, 2024
@MarcoGorelli MarcoGorelli converted this issue into discussion #1657 Dec 24, 2024
@MarcoGorelli MarcoGorelli pinned this issue Dec 24, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

1 participant