You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user doesn't have the 'numexpr' engine installed on his computer, everything is fine, because in that case pandas.eval will use the 'python' engine instead, but otherwise, the following line of code
Great! Seems like the solution is just add engine='python' to the end of the .query() call. If you're interested in submitting a PR for this that would be great! Let me know if you're up for it.
It turns out that the 'numexpr' engine, which is used by default by pandas.eval cannot handle pd.Series for an unknown reason -> https://stackoverflow.com/questions/51878316/pandas-python-series-objects-are-mutable-thus-they-cannot-be-hashed-in-query-me.
When a user doesn't have the 'numexpr' engine installed on his computer, everything is fine, because in that case pandas.eval will use the 'python' engine instead, but otherwise, the following line of code
will raise the following error
TypeError: 'Series' objects are mutable, thus they cannot be hashed
The text was updated successfully, but these errors were encountered: