-
Notifications
You must be signed in to change notification settings - Fork 25
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
[BUG]: pip install on windows failing #65
Comments
edit: redacted |
The original issue was on my end. It seems that I can get everything working now and am getting the same results identically in both windows and linux now. edit: I updated this issue for what I found along the way. This testing was useful though because I found that I cannot install
to What do you think @aburrell? |
Hmmm... and I am guessing from this command that there's no 32/64 agnostic command? My first instinct is to say, "let's create a branch and I'll upload a testable pip release candidate for you". But we need to make sure the setup config won't break appveyor or people with 64-bit systems, or are not on Windows! I think adding instructions may be the way to go. I saw this example for using/abusing pip. Does it work for you?
Above solution from: https://stackoverflow.com/questions/3297254/how-to-use-mingws-gcc-compiler-when-installing-python-package-using-pip Also, did you try the pip install from TestPyPi? That will get you the current release candidate. From your statement above it looks like you didn't, but am also not sure if it will matter in this instance. |
After some sleep, I tried again. I had already tried the suggested command, specifically this:
but it doesn't work. Looking at the logs, it seems to try to build all the dependencies in
So if I tell pip to ignore PEP 517, that fixes things:
So adding
So probably the best solution to all of this is just to document this idiosyncrasy for windows users? |
Yes, I think that's the best way forward. |
Sounds good. I'll make a commit to the documentation later today. Thanks! |
Looks like the best solution for Windows users might be to do this: https://wiki.python.org/moin/WindowsCompilers#GCC_-_MinGW-w64_.28x86.2C_x64.29 I've tested this and I can now simply run |
I am on Windows 11 and was having trouble installing apexpy as part of a conda environment.yml file. There were no errors during installation but I got the Everything appears to work if I take the following steps:
|
Describe the bug
pip install .
doesn't work out of the box with Windows 10 and the mingw32 compiler.To Reproduce
Steps to reproduce the behavior:
Grab this commit:
git clone git+https://github.com/aburrell/apexpy.git@4a5b2d696b1c905b77e4115cbe9438f41c0c6740
(This is the latest, about to be merged in for 1.1.0 release)Try to
pip install .
and then try importingimport apexpy
in a python shell and get this result:Python 3.7.9 (default, Aug 31 2020, 17:10:11) [MSC v.1916 64 bit (AMD64)] :: Anaconda, Inc. on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import apexpy
C:\tools\miniconda3\envs\py37\lib\site-packages\apexpy\apex.py:19: UserWarning: fortranapex module could not be imported, so apexpy probably won't work. Make sure you have a gfortran compiler. Wheels installation assumes your compiler lives in /opt/local/bin" assumes your compiler lives in /opt/local/bin"]))
Traceback (most recent call last):
File "", line 1, in
File "C:\tools\miniconda3\envs\py37\lib\site-packages\apexpy_init_.py", line 3, in
from .apex import Apex, ApexHeightError
File "C:\tools\miniconda3\envs\py37\lib\site-packages\apexpy\apex.py", line 20, in
raise err
File "C:\tools\miniconda3\envs\py37\lib\site-packages\apexpy\apex.py", line 14, in
from . import fortranapex as fa
ImportError: DLL load failed: The specified module could not be found.
Expected behavior
The pip install command should work fine.
Computer (please complete the following information):
Windows 10, miniconda python3.7 with mingw32 compiler installed.
The text was updated successfully, but these errors were encountered: