Skip to content
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

Numpy conda package broken inside tox on Windows, Python 3.7/3.8 #184

Closed
goerz opened this issue Feb 7, 2020 · 8 comments
Closed

Numpy conda package broken inside tox on Windows, Python 3.7/3.8 #184

goerz opened this issue Feb 7, 2020 · 8 comments

Comments

@goerz
Copy link

goerz commented Feb 7, 2020

The conda-package for numpy does not work on Windows inside a tox environment. See cross-reference numpy/numpy#15537

@jan-janssen
Copy link
Member

I tried to trigger a new build - hopefully that is sufficient #224

@jan-janssen
Copy link
Member

For me the issue seems to be fixed now.

@jakirkham
Copy link
Member

Thanks for the update. Let’s go ahead and close then

@basnijholt
Copy link

I still see the issue described by @goerz in the upstream issue numpy/numpy#15537 for v1.20.1:

E   ImportError: 
E   
E   IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
E   
E   Importing the numpy C-extensions failed. This error can happen for
E   many reasons, often due to issues with your setup or how NumPy was
E   installed.
E   
E   We have compiled some common reasons and troubleshooting tips at:
E   
E       https://numpy.org/devdocs/user/troubleshooting-importerror.html
E   
E   Please note and check the following:
E   
E     * The Python version is: Python3.8 from "d:\a\1\s\.tox\py38\python.exe"
E     * The NumPy version is: "1.20.1"
E   
E   and make sure that they are the versions you expect.
E   Please carefully study the documentation linked above for further help.
E   
E   Original error was: DLL load failed while importing _multiarray_umath: The specified module could not be found.

@rgommers
Copy link
Contributor

So did you activate your conda environment, like the solution numpy/numpy#15537 (comment) says?

@basnijholt
Copy link

basnijholt commented Feb 26, 2021

Unfortunately, I am not in control of that. It happens for me when using Tox with tox-conda in our CI.

The related issue is tox-dev/tox-conda#37.

@jakirkham
Copy link
Member

It would be good if someone could reproduce the issue without tox. If that's not possible, it may simply be a tox issue

@basnijholt
Copy link

I don't have access to a Windows machine :(

However, the following might give someone with more knowledge than me some clues.

Using set CONDA_DLL_SEARCH_MODIFICATION_ENABLE=1 while using numpy from the defaults channel fixed the issue. The conda docs describe what this does, however, there it's the solution to a (seemly?) different problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants