-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Issue with NumPy, macOS 11 Big Sur, Python 3.9.1 Does pipenv not use the latest pip? #4564
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
Comments
Seem related to the bug reported at NumPy here: #17784 |
+1 exact same issue and error trace for me @shanewilkins thank you for pointing me in the right direction. The issue was in fact that pipenv was using You can just manually update pipenv's pip with After this the numpy install works for me. **Edit - Actually, the numpy install only works with |
@jaymegordo Upgrading pipenv's pip did not work. |
I can also confirm that upgrading pipenv pip did not work for me. |
Any clue why pipenv lock fails? |
@jo3p I think it has something to do with how Big Sur changed how some system libraries are stored now. FWIW I'm still having the same issue, here's the start of my tb:
Then a bunch more lib errors after that, exact same error trace as @shanewilkins's original post |
I think pipenv's vendored That will at least allow use of the precompiled wheel for numpy, kicking the separate compiling-from-source issue down the road a bit. |
Hi, |
@radekerben thank you! That actually worked for me too, I can now successfully run |
This also worked for me as well. Thanks @radekerben 🥇 |
You need packaging 20.9 for full Big Sur (Intel and Apple Silicon) support. 20.7+ for just Intel Big Sur. Or, of course, you can tell macOS to report a version number of 10.16 instead of 11 using Any chance we can get a bump (master has 20.8) and version release? |
Thanks for the investigation. It works for me and I just upgraded to the latest Big Sur 11.3 |
This is because packaging expects |
It is already done. I am seeking for people help testing the master branch before i can make a release |
How can we help test? |
Let me know how can I help test |
This issue seems fixed in the latest python release 3.9.5 |
Just tested with python 3.9.5 and still having the problem (setting |
Does anyone have a good Universal2 wheel to test? I have a couple, like boost-histogram, but they require NumPy, and NumPy doesn't have a universal2 or arm64 for macOS wheel yet. It looks like packaging is vendored at 20.8; 20.9 is required to support Apple Silicon property. But I need a good non-NumPy requiring package to test.
Starts building from source, which of course it should, as there are no supported wheels. |
@frostming could you please bump packaging to 20.9? Also, are you on the PyPA discord server? Would it make sense to use the |
If this is an issue on M1 + MacOS, that's possibly also because of numpy/numpy#18143. |
pipenv was just released without bumping packaging to 20.9. The docs clearly said all dependencies would be bumped before releasing, so bump PRs were discouraged. 😭 I'm trying to help with Universal2 wheel rollout, and packaging 20.9 (and pip 21.0.1) are needed to properly handle some universal2 wheels. |
It's not exclusively. I have an older MacBook with an Intel chip and run into the same issue. |
A lot of work has gone into making macOS Big Sur work, but it requires the latest dependencies. Pipenv was released without the "bump all dependencies" step described in its docs, so sadly, it still doesn't understand that "11.0" is a valid macOS version. If you set |
works on apple silicon with terminal started under rosetta simulation too |
It works. However, it's not exactly the ideal solution in my humble opinion. |
I have faced the same problem but, it seems works when I am using latest version of numpy. In other words, whenever tried to install older version like 1.15.2 it gives me installation failure. So technically it should work when you are using the latest one. |
This should be resolvable on |
In my case the issue was that I hadn't agreed to the xcode licensing agreement. I fixed the issue by typing I was then prompted to update my xcode CLI tools, which was also necessary since further runs of I tried repeatedly to run the software installation, but the same error kept popping up until I found this Stack Overflow thread which suggested running the following command:
After that it finally worked. |
Uh oh!
There was an error while loading. Please reload this page.
People are probably already aware of this issue, but adding my $0.02 as to what I think may be going on.
In a nutshell: NumPy fails to build on OS 11 and python 3.9.1. The error message is attached below, but NumPy is installed and works. (you can
import numpy as np
from a python interpreter) However, if you try to import numpy in a notebook, you get an error message saying that numpy is using a buggy "accelerate" backend.The error about the backend occurs when numpy is being built from source incorrectly instead of using the provided wheel. That known issue was supposedly fixed in a pip upgrade (20.3). However, I get the same error below, even when I have updated pip to 20.3.
However, when i create a new pipenv environment, it defaults to pip 20.2. So my guess is that even if I subsequently update pip to 20.3, that
pipenv install numpy
is using the old version of pip.Can anybody confirm and/or offer a workaround?
The text was updated successfully, but these errors were encountered: