-
Notifications
You must be signed in to change notification settings - Fork 36
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
Change the arguments position of pl$Series
with Python Polars
#903
Comments
@grantmcdermott Any thoughts on this? |
Oof, I think you're correct and there's probably no other way around it. Consistency across r-polars and py-polars has always been a (the?) North Star for this project, so this is just an unfortunate cost. |
If we do this, yes we should add a deprecation warning for a few releases before changing the behavior. However, I'd rather wait for pola-rs/polars#13405 to be settled before going forward with this. It seems like the order of arguments is unlikely to change but let's wait for a final decision |
pl$Series
should be change to match with Python Polars?pl$Series
should be changed to match with Python Polars?
Thanks both.
If a change is made in Python, I think it can be reverted, but shouldn't it be fixed that the function argument is incorrect right now? |
I don't understand your point. Right now, they |
I'm just suspicious that it needs to be changed because they're there right now. |
pola-rs/polars#13405 has been marked as "not planed", so we will change the argument order. |
pl$Series
should be changed to match with Python Polars?pl$Series
with Python Polars
In Python:
In R:
And the document says:
https://github.com/pola-rs/polars/blob/25d0a2f028bd2de0bdc140a2c040f2e2b4c2f46e/py-polars/polars/series/series.py#L225-L227
I suspect that
as_polars_series
should be used as a function that takes a vector as its first argument, andpl$Series
should be rewritten in the argument position to match Python.This would be a very huge breaking change, so we will probably have to continue warnings for several months and then make the change.
@etiennebacher Thoughts?
The text was updated successfully, but these errors were encountered: