'ValueError: numpy.ufunc has the wrong size, try recompiling' when install pyxDamerauLevenshtein
See original GitHub issueHow to reproduce:
docker run -it --entrypoint=/bin/bash python:3.6
to have a clean environment;- pip install numpy pyxdameraulevenshtein
- call python
>>> import pyxdameraulevenshtein
Result: Traceback (most recent call last): File “<stdin>”, line 1, in <module> File “init.pxd”, line 885, in init pyxdameraulevenshtein ValueError: numpy.ufunc has the wrong size, try recompiling. Expected 192, got 216
pyxDamerauLevenshtein==1.5
Issue Analytics
- State:
- Created 5 years ago
- Comments:27 (3 by maintainers)
Top Results From Across the Web
'ValueError: numpy.ufunc has the wrong size, try recompiling ...
rasa_core 's requirements.txt file already installs NumPy 1.16.0, so I just installed pyxDamerauLevenshtein after it, and it worked just fine.
Read more >ValueError: numpy.ufunc has the wrong size, try recompiling
The issue is with an old version of numpy being installed on your system. In my case it turned out conda was selecting...
Read more >Numpy.ufunc has the wrong size, try recompiling
When I run “Example: Generating phase diagrams”, something wrong occurred: Traceback (most recent call last):
Read more >numpy.ufunc has the wrong size, try recompiling" 解决方法
解决方法:升级numpy即可:pip install -U numpy. ... ValueError: numpy.ufunc has the wrong size, try recompiling. Expected 192, got 216.
Read more >Python引入pandas报错ValueError: numpy.ufunc has ... - 博客园
Python引入pandas报错ValueError: numpy.ufunc has the wrong size, try recompiling 原因:这是因为Python 包的版本问题,例如.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@gfairchild Took some time to get to it (needed new credits, and a new build), but I can confirm 1.5.4 worked immediately for me.
@gfairchild I have updated the version number for next build so we will see 😃