Closed martassimoes closed 3 months ago
You mean numpy
version 1.19?
Can you tell exactly which versions you are using? including of TIGRE? This issue should have been fixed a bit ago (#430)
You mean
numpy
version 1.19?
yes.
I assumed. Can you tell us python, cython and TIGRE version you are running? as mentioned, I thought this was solved already, so maybe you are running an old version.
Its also strange, because np.int
was deprecated in numpy 1.20, but you say you are running 1.19, so I am not sure where the error comes from, as I can't see anywhere in TIGRE using np.int
(maybe I am missing something!) nor should it error in numpy 1.19, if there was anywhere.
Hi. When I run the code in demo 3, point 6 of the step-by-step instructions in the Installation Instructions for Python for Windows section, I get the following error:
ImportError Traceback (most recent call last)
As I said in my email, the error before
ImportError: cannot import name 'int' from 'numpy' (C:\Users\ASUS\anaconda3\lib\site-packages\numpy_init_.py)
is because you are using a numpy
that doesn't have np.int
(i.e. you are not using 1.19 as you think you are), as Scipy errors. Clearly also your Scipy and numpy are not compatible. This is likely because you have been fiddling with versions too much and you have lost control of which one you have.
The second error
ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject.
Suggests that the binary (compiled files after pip install .
) are not compatible with the current version. This almost surely happens because you did pip install .
for one version of numpy/scipy etc, but you did then change them, thus the binary file is incompatible.
Hi. When I try to import the 'tigre' module in Python version 1.19, I encounter this error:
cannot import name 'int' from 'numpy' (C:\Users\ASUS\anaconda3\lib\site-packages\numpy__init__.py)
However, I have already updated and downgraded to other versions, and a different error still appears: .
numpy.ndarray size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject
Has anyone else experienced this?