-
Notifications
You must be signed in to change notification settings - Fork 34
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
ImportError: cannot import name '_non_reducing_slice' from 'pandas.core.indexing' #168
Comments
Thanks for reporting, will be fixed in the next release. |
Had the same error with conda installation, as of Apr 2, 2021. Manually changing
Hope it'll be fixed in the conda release. |
After loads of trouble with the bioconda build system, version 0.15.3 (where this is fixed) is now available via conda. |
With the newest pandas versions (1.3.0 onwards) the function is now located in |
I installed with v0.16.1. It also has the same error. |
I've hit this too, while trying to run the unit tests. I've added another try-catch to import non_reducing slice from |
Is it possible to reopen this issue? I am coming across this too |
Hi
I recently installed gimmemotifs (see version below) using conda as recommended.
Installation step went well without any errors.
But then calling
bash gimme motifs -h
to test installation got me this error: "ImportError: cannot import name '_non_reducing_slice' from 'pandas.core.indexing'" (see Error logs below).Seems pandas has removed the leading underscore to the offending function and replaced
_non_reducing_slice
bynon_reducing_slice
as shown in their repo herePatching report.py with the new function name fixed it.
Please, can you fix it by replacing the function by its new name in report.py?
Thanks in advance
@jos4uke
To Reproduce
Please see Installation information section to reproduce.
Expected behavior
calling help on gimme motifs using the -h switch should have returned the expected help message:
Error logs
Installation information:
bash mamba create -n gimmemotifs python=3 gimmemotifs
The text was updated successfully, but these errors were encountered: