BUG: windows dll install directory changed from scipy/.libs to scipy.libs
See original GitHub issueDescribe your issue.
From scipy 1.9.1 to scipy 1.9.3 the directory used to install dlls on windows changed. scipy-1.9.1: dlls are installed in …/site-packages/scipy/.libs scipy-1.9.3: dlls are installed in …/site-packages/scipy.libs
This causes pyinstaller builds using scipy-1.9.3 to fail as the expected dll location changed.
If this change was intented I will file a bug report with pyinstaller to update the scipy installer hook.
Reproducing Code Example
None
Error message
None
SciPy/NumPy/Python version information
1.9.3 1.23.1 sys.version_info(major=3, minor=10, micro=6, releaselevel=‘final’, serial=0)
Issue Analytics
- State:
- Created 10 months ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Missing DLL dependencies, scipy 1.6.3 · Issue #14002 - GitHub
I have scipy version 1.6.3 installed from conda-forge: scipy 1.6.3 py38he847743_0 ... The DLL file mentioned in the error message below exis.
Read more >Can't import dll module in Python - windows - Stack Overflow
This lib that I've already compiled and successfully imported using the same version of Python on Linux machines, doesn't like w10 at all....
Read more >Building from source on Windows — SciPy v1.7.0 Manual
This is very good news: you have successfully built OpenBLAS! Installing OpenBLAS¶. Look for the lib folder in the folder you used as...
Read more >LAPACK for Windows - ICL UTK
Download the BLAS and LAPACK dll and lib that correspond to your need. ... change the properties "Linker > General > Additional Library...
Read more >sys — System-specific parameters and functions — Python ...
This module provides access to some variables used or maintained by the interpreter and to functions that interact strongly with the interpreter.
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 Free
Top 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
It’s not
cibuildwheel
that controls where the bundled dlls end up, it’s down to the tool that repairs the wheel. For Windows this isdelvewheel
, for macOS it’sdelocate
and on Linux it’sauditwheel
. One can use the-L, --lib-sdir
option to control where the vendored dlls are stored, butpackage-name/.libs
is the default. I believe this is the same behaviour asdelocate
except that tool usespackage-name/.dylibs
It’s whatever the default of the tools doing the shared library vendoring is. I don’t think we care too much either way. If I had to choose, I’d probably stay with
.libs
, but it’s not a big deal.Same here