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
ModuleNotFoundError: No module named 'numpy.core._multiarray_umath' #12825
Comments
It seems like you are unpickling an array which was saved in numpy 1.16 in numpy 1.13.3 |
This one looks like a real bug. I think we might need to override |
I believe @tzickel is correct. I just regenerated % ipython3
Python 3.6.7 (default, Oct 22 2018, 11:32:17)
Type "copyright", "credits" or "license" for more information.
IPython 5.5.0 -- An enhanced Interactive Python.
? -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help -> Python's own help system.
object? -> Details about 'object', use 'object??' for extra details.
In [1]: import pandas as pd
In [2]: df = pd.read_hdf("data.h5")
In [3]: df.columns
Out[3]:
Index(['aonames', 'atombasis', 'atomcharges', 'atomcoords', 'atommasses',
'atomnos', 'charge', 'coreelectrons', 'enthalpy', 'entropy',
'freeenergy', 'gbasis', 'geotargets', 'geovalues', 'grads', 'homos',
'jobfilename', 'metadata', 'mocoeffs', 'moenergies', 'moments',
'mosyms', 'mult', 'natom', 'nbasis', 'nmo', 'optdone', 'optstatus',
'polarizabilities', 'pressure', 'scfenergies', 'scftargets',
'scfvalues', 'temperature', 'vibdisps', 'vibfreqs', 'vibirs',
'vibsyms'],
dtype='object')
In [4]: df["freeenergy"].head()
Out[4]:
0 -228.614123
1 -229.062884
2 -552.464074
3 -552.010916
4 -552.006776
Name: freeenergy, dtype: float64 I'm closing this since I belive it's solved. Thanks @tzickel! |
I do not believe this error is resolved. I'm not using any pickle files and I am getting this exact same error. I have this error recently since a few changes on my MAC. I followed all the best practices and can't seem to resolve this error. Upgraded to MAC High Sierra (10.13.6) installed both python 3.6 and python 3.7 to run side by side using home-brew and followed the guidelines presented here: setup new virtual env to use python 3.6.5 and a bunch of other modules. This error occurs in the virtual environment. Both notebooks and command line python code generate the error. The python code runs 100% correctly with no other errors than this message. python my_py_file.py I deleted and recreated the venv but the error persists. Likely all the code continues to run without any other errors. I'm not sure what to do next. If there is a solution, please let me know otherwise IMHO this issues should not be closed. A similar issue is being tracked here: |
FYI, I just resolved this issue by forcing a reinstall of numpy and pandas as follows: pip install --upgrade --force-reinstall numpy==1.14.5 No more error message. |
Solved this issue!
Traceback (most recent call last):
numpy 1.16.0
Hope this helps! |
Been having this issue and this solved the problem for me, too. Thanks! |
Update numpy with pip and it will work: pip install --upgrade numpy |
@mlsmall thanks. it is magic. |
Hi,
I got a problem similar to #11871. I recently installed numpy 1.16.0 but then I needed to downgrade and now I keep getting
ModuleNotFoundError: No module named 'numpy.core._multiarray_umath'
.The example below was working fine a week ago or so.
I actually ended up removing ALL Python packages (instructions here) and reinstalling them one by one using
apt-get
(Ubuntu 18.04.1 LTS), except foripyparallel
andopenbabel
, which were installed usingpip
(I'm pretty sure both are unrelated to the problem). The example below was run after all this clean-up.It seems that a lot of people are having this issue lately, with different packages:
Reproducing code example and error message:
Below is a IPython session that shows the error:
Some relevant files and versions:
Numpy/Python version information:
I'm using Ubuntu 18.04.1 LTS:
% uname -a Linux mothership 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
In #11871 @mattip mentioned that
How come I get this error even though I have numpy 1.13.3? Thanks for all the help!
The text was updated successfully, but these errors were encountered: