-
Notifications
You must be signed in to change notification settings - Fork 122
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
fix: address &
/ |
operator errors for PySpark / chore: use F.lit in maybe_evaluate for pyspark, like we do for duckdb
#1872
fix: address &
/ |
operator errors for PySpark / chore: use F.lit in maybe_evaluate for pyspark, like we do for duckdb
#1872
Conversation
&
/ |
operator errors for PySpark / chore: use F.lit in maybe_evaluate for pyspark, like we do for duckdb
@@ -55,7 +54,6 @@ def __init__( | |||
self._returns_scalar = returns_scalar | |||
self._backend_version = backend_version | |||
self._version = version | |||
self._kwargs = kwargs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we were only using these _kwargs
for std
and var
, and even then, #1870 would address those. I think we can get rid of them?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice one! Let's ship it and merge with #1870
self._native_series.dtype, | ||
dtype_backend, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch!
What type of PR is this? (check all applicable)
Related issues
Checklist
If you have comments or can explain your changes, please do so below