GeezerVison is showing github.com — cannot import scipy with WinPython 2020-01 on Windows 10 · Issue #828 · winpython/winpython
cannot import scipy with WinPython 2020-01 on Windows 10 #828Descriptionhere's what I get in both Python 3.8.2 and 3.7.7 after executing import scipy:
Traceback (most recent call last):
File "<ipython-input-1-4363d2be0702>", line 1, in <module>
import scipy
File "C:\WPy64-3820\python-3.8.2.amd64\lib\site-packages\scipy\__init__.py", line 156, in <module>
from . import fft
File "C:\WPy64-3820\python-3.8.2.amd64\lib\site-packages\scipy\fft\__init__.py", line 76, in <module>
from ._basic import (
File "C:\WPy64-3820\python-3.8.2.amd64\lib\site-packages\scipy\fft\_basic.py", line 1, in <module>
from scipy._lib.uarray import generate_multimethod, Dispatchable
File "C:\WPy64-3820\python-3.8.2.amd64\lib\site-packages\scipy\_lib\uarray.py", line 27, in <module>
from ._uarray import *
File "C:\WPy64-3820\python-3.8.2.amd64\lib\site-packages\scipy\_lib\_uarray\__init__.py", line 114, in <module>
from ._backend import *
File "C:\WPy64-3820\python-3.8.2.amd64\lib\site-packages\scipy\_lib\_uarray\_backend.py", line 15, in <module>
from . import _uarray # type: ignore
ImportError: DLL load failed while importing _uarray: The specified module could not be found.
Activitystonebig commented on Apr 5, 2020 Hum, that is strange. Are you on Windows 10 ? stonebig commented on Apr 5, 2020 I found someone with the opposite problem ... maybe try the opposite, try with Anaconda
numpy/numpy#12957 (comment)
Another internet suggests maybe your path variable is too long dlzcn commented on Apr 8, 2020 Run perfectly on my PC, but failed with same errors on my laptop. Both of them are running Windows 10. I checked length of the path variable on my PC, it is 1715 characters. Not sure the size of the variable on my laptop. stonebig commented on Apr 8, 2020 Hum, maybe search then try your question on stackoverflow.
Another shot in the dark would be to retry after moving your directory:
- to you user space: C:/users/???/
- or to a non-C drive
other ideas are: another Python system installed create troubles, your initial installation has lost a dll, ... stonebig commented on Apr 8, 2020 stonebig commented on Apr 8, 2020 hum, that may just be a python-3.8 change : now, Python- 3.8 doesn't look for a dll out of system unless explicitly told.
as a blind guess, I suggest you retry with a python-3.7 distribution, as it tackles DLL differently dlzcn commented on Apr 8, 2020 Switched to python-3.7 distriubtion.
File "D:\python\WPy64-3770\python-3.7.7.amd64\lib\site-packages\sklearn_init_.py", line 82, in
from .base import clone
File "D:\python\WPy64-3770\python-3.7.7.amd64\lib\site-packages\sklearn\base.py", line 20, in
from .utils import IS_32BIT
File "D:\python\WPy64-3770\python-3.7.7.amd64\lib\site-packages\sklearn\utils_init.py", line 20, in
from scipy.sparse import issparse
File "D:\python\WPy64-3770\python-3.7.7.amd64\lib\site-packages\scipy_init_.py", line 156, in
from . import fft
File "D:\python\WPy64-3770\python-3.7.7.amd64\lib\site-packages\scipy\fft_init_.py", line 76, in
from ._basic import (
File "D:\python\WPy64-3770\python-3.7.7.amd64\lib\site-packages\scipy\fft_basic.py", line 1, in
from scipy._lib.uarray import generate_multimethod, Dispatchable
File "D:\python\WPy64-3770\python-3.7.7.amd64\lib\site-packages\scipy_lib\uarray.py", line 27, in
from .uarray import *
File "D:\python\WPy64-3770\python-3.7.7.amd64\lib\site-packages\scipy_lib_uarray_init.py", line 114, in
from ._backend import *
File "D:\python\WPy64-3770\python-3.7.7.amd64\lib\site-packages\scipy_lib_uarray_backend.py", line 15, in
from . import _uarray # type: ignore
ImportError: DLL load failed: The specified module could not be found. stonebig commented on Apr 8, 2020 Well, I'm out of ideas at the moment. Having a working PC and a not-working Laptop shall allow you to enumerate what's different between them: tiny memory, very very slow processor, another Python distro, a virulant anti-virus, ... dlzcn commented on Apr 8, 2020 makazhan commented on Apr 8, 2020 stonebig commented on Apr 8, 2020 stonebig commented on Apr 8, 2020 So the vcruntime140_1.dll will be in next binaries, even if I'm not sure it solves the problem.
It's a bit odd to have every user needing to install a microsoft executable. stonebig commented on Apr 8, 2020 dlzcn commented on Apr 8, 2020 stonebig commented on Apr 8, 2020
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|