-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
COMPAT: show warning when using numexpr not installed and defaulted #12749
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
this was fixed in 0.18.0. previously if you tried to use |
xref #12511 |
The problem is obviously not fixed (or not correctly) for the case I describe because it happens with pandas 0.18.0. It's annoying to see a post closed without discussion. :( |
Note that I also read the code in master before opening this issue. |
@sciunto so what is the reproducible example then. are you sure you are using 0.18.0 |
also you didn't read our issue submission guidelines. I don't see |
I suppose you are doing this?
|
I guess that could be more friendly. Though maybe should show a |
Yes I'm sure...
Please, read carefully my first post. |
well, you can submit a pull-request if you would like. I DID read your first post. we have 1600 issues. |
cc @mrocklin
Hi,
Context:
Right now, pandas treats numexpr as an optional dependency. I'm a packager for archlinux, and recently, I got a feedback on the dask package saying that numexpr was missing as a dependency of this package. https://aur.archlinux.org/packages/python-dask/
However, dask does not explicitly on numexpr. The reason is detailed below.
Analysis:
In
pandas.computations
,eval()
takes an optional argumentengine='numexpr'
.If numexpr is not install, then any call with default arguments will raise an exception importError from the function
_check_engine
in pandas/computations/eval.py.eval()
is called (at least) from query, that's why we are in trouble if we run dask's test without numexpr.RFC:
Here is the question: is numexpr really an optional dependency since it's the default argument?
I would say no, but comments are open :)
From the dask devs point of view, they do not have to mark numexpr as a dependency because they do not use it explicitly. To me, they can expect that default arguments from pandas work out of the box.
From the pandas packager (not me), pandas says that numexpr is optional, treated as optional. No problem here too, he followed the guidelines.
I see two options:
The text was updated successfully, but these errors were encountered: