Accept macosx_10_9 platform for Big Sur

[memeplex]

Environment

• 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

1. pip install numpy
2. Tries to build.
3. Fails to build

Instead:

1. pip install --platform macosx_10_9_x86_64 --only-binary=:all: --target=/tmp numpy
2. Downloads wheel
3. 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.

[memeplex]

I've been using this horrible hack:

    version_str, _, cpu_arch = platform.mac_ver()  # type: ignore
    version_str = "10.15.1"

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?

[pradyunsg]

This is blocked on pypa/packaging#319.

[MarioCatuogno]

Don't know if this can help, but I'm getting an error if I try to install pandas via pip3 with a clean installation of macOS Big Sur and Python3.9. If I use one of the following command I'm getting the error below:

pip install pandas
pip3 install pandas
pip3 install pandas --no-build-isolation --no-cache-dir
sudo pip3 install pandas --no-cache-dir

`
Getting requirements to build wheel ... error
ERROR: Command errored out with exit status 1:
command: /usr/local/opt/python@3.9/bin/python3.9 /usr/local/lib/python3.9/site-packages/pip/_vendor/pep517/_in_process.py get_requires_for_build_wheel /var/folders/zv/0q58rjv549bd4qjdqlrwlvl40000gn/T/tmpzr3sthd6
cwd: /private/var/folders/zv/0q58rjv549bd4qjdqlrwlvl40000gn/T/pip-install-pvlaq6iq/pandas
Complete output (23 lines):
init_dgelsd failed init
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/pip/_vendor/pep517/_in_process.py", line 280, in
main()
File "/usr/local/lib/python3.9/site-packages/pip/_vendor/pep517/_in_process.py", line 263, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
File "/usr/local/lib/python3.9/site-packages/pip/vendor/pep517/in_process.py", line 114, in get_requires_for_build_wheel
return hook(config_settings)
File "/private/var/folders/zv/0q58rjv549bd4qjdqlrwlvl40000gn/T/pip-build-env-ly4c8n5/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 149, in get_requires_for_build_wheel
return self.get_build_requires(
File "/private/var/folders/zv/0q58rjv549bd4qjdqlrwlvl40000gn/T/pip-build-env-ly4c8n5/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 130, in get_build_requires
self.run_setup()
File "/private/var/folders/zv/0q58rjv549bd4qjdqlrwlvl40000gn/T/pip-build-env-ly4c8n5/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 253, in run_setup
super(BuildMetaLegacyBackend,
File "/private/var/folders/zv/0q58rjv549bd4qjdqlrwlvl40000gn/T/pip-build-env-ly4c8n5/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 145, in run_setup
exec(compile(code, file, 'exec'), locals())
File "setup.py", line 488, in
import numpy as np
File "/private/var/folders/zv/0q58rjv549bd4qjdqlrwlvl40000gn/T/pip-build-env-ly4c8n5/overlay/lib/python3.9/site-packages/numpy/init.py", line 286, in
raise RuntimeError(msg)
RuntimeError: Polyfit sanity test emitted a warning, most likely due to using a buggy Accelerate backend. If you compiled yourself, see site.cfg.example for information. Otherwise report this to the vendor that provided NumPy.
RankWarning: Polyfit may be poorly conditioned

---

ERROR: Command errored out with exit status 1: /usr/local/opt/python@3.9/bin/python3.9 /usr/local/lib/python3.9/site-packages/pip/_vendor/pep517/_in_process.py get_requires_for_build_wheel /var/folders/zv/0q58rjv549bd4qjdqlrwlvl40000gn/T/tmpzr3sthd6 Check the logs for full command output.
`

These are the only packages actually installed:

Package Version

---

pip 20.2.4
setuptools 50.3.2
wheel 0.35.1

[memeplex]

@MarioCatuogno complex builds may fail because of many reasons and usually fail... But this report is about having to build those packages at all instead of using a pre-built wheel. The cause is clear, pip is not seeing a wheel built for MacOS 10.x as valid for MacOS 11.

[uranusjr]

Marking the comment as Off-topic since it is. @MarioCatuogno the error you’re seeing is a Numpy issue and needs to be reported there. pip cannot do anything about it.

[jaredrcleghorn]

@pradyunsg what do you mean by blocked?

[uranusjr]

In project management terminology, “blocked” means something (“blocking” issue) needs to be done first before the thing at hand (“blocked” issue) can be addressed.

[jaredrcleghorn]

@uranusjr Gotcha, so the problem is in packaging, not pip directly? Or will it need to be addressed in both?