-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Dataframe.query uses numexpr even when 'compute.use_numexpr' is False #32556
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
Comments
I stumbled into this issue as well. I am adding a minimal example which can be used as a non-regression test: import pandas as pd
pd.set_option("compute.use_numexpr", False)
df = pd.DataFrame(
{"A": [True, False, True, False, None, None],
"B": [1, 2, 3, 4, 5, 6]}
)
df.query('A.isnull()') |
After checking #33006 I am not sure what is the right fix and what was the initial semantic behind @jreback Since you commented on the PR, maybe you can have some insights. |
@glemaitre |
The following demonstrates issue and raises on master:
Can resolve this as in #33006 with the above code as a test. |
Hello, I'm Yash and I've been asked to contribute to an open source project for my Software Development course. I'd be interested to work on this issue and it'd be great if I could be assigned to this. Thank you. |
you can assign yourself with /take |
@jreback I tried doing that but I'm still unable to assign myself. |
@jreback Thank you so much. I'll have a look. |
take |
take |
take |
Code Sample, a copy-pastable example if possible
throws with pandas 1.0
Problem description
Dataframe.query fails when using UInt* dtypes see #25369 (comment).
My first idea to solve this was to disable numexpr but this isn't enough, one has to pass
engine="python"
to forcefully disable numexpr when callingquery
The text was updated successfully, but these errors were encountered: