Accept macosx_10_9 platform for Big Sur
See original GitHub issueEnvironment
- pip version: 20.2.4
- Python version: 3.8.6
- OS: MacOS 11 (Big Sur)
Description
The update to Big Sur changed the major version of MacOS. AFAICS this is not really related to internals but more because of face lift and commercial concerns. But it’s forcing pip to build everything from sources (which is not only slow but tends to fail for complex packages like numpy).
I’m using the --platform flag as a workaround but it requires to also specify --target and --only-binary, which is not really convenient.
Expected behavior
Wheels for previous versions are used.
How to Reproduce
pip install numpy- Tries to build.
- Fails to build
Instead:
pip install --platform macosx_10_9_x86_64 --only-binary=:all: --target=/tmp numpy- Downloads wheel
- Works fine
Output
This is not really relevant, I’m not concerned with the reasons the build failed (related to blas and lapack) but because the build happens at all.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:11
- Comments:14 (6 by maintainers)
Top Results From Across the Web
macOS Big Sur - Technical Specifications - Apple Support
General Requirements. OS X 10.9 or later; 4GB of memory; 35.5GB available storage on macOS Sierra or later*; Some features require an Apple ......
Read more >How to Allow Apps from Anywhere on macOS Big Sur [Tutorial]
How to Allow Apps from Anywhere on macOS Big Sur [Tutorial]Terminal Commands:Restore "Anywhere" button: sudo spctl --master-disable Hide ...
Read more >Big Sur on older Macs [2008-2013] ULTIMATE GUIDE ...
You can Install macOS Big Sur on your 2008-2013 Unsupported Mac with this ULTIMATE GUIDE!!! I will show you how to use OpenCore...
Read more >macOS Big Sur: A cheat sheet - TechRepublic
Apple now has Rosetta 2, an emulation app, that will emulate the environment as needed to allow apps that have not yet updated...
Read more >macOS 11 (Big Sur), OS12 (Monterey) and M1 Support for ...
Product Big Sur on Intel Big Sur on M1 Big...
Pro Tools Intro 2022.9 and later 2022.9 and later * 11.2.3
Pro Tools | First...
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

This has been fixed in https://github.com/pypa/packaging/pull/319 and related PRs in CPython so I guess the fix will be released soon-ish. It “just” needed someone with the time an knowledge to review the pull requests to add support for Big Sur to CPython related repos. Ironically the person who reviewed that last PR in this case works at Microsoft.
If Apple paid more full time employees to work as core developers on major open source projects such as CPython such fixes would be faster included when they release a new version of their OS.
Pending that, the easy workaround is just to wait for some time before upgrading to a new OS while open source maintainers do the work at their own pace instead.
I’ve been using this horrible hack:
in site-packages/pip/_vendor/packaging/tags.py and after installing my environments everything seems to work fine.
The solution to this issue may be in changing pip or in building wheels for 11, this depends on the level of compatibility of MacOS 11 wrt 10.
This is OT, but do you know why there aren’t wheels for 11 yet and how long does the build usually take?