Description
I am a NumPy developer and do not use brew. We have been getting reports across the scientific python ecosystem (matplotlib, numpy, pandas, scipy, and more) that python3.9 -m pip install numpy is failing to properly install NumPy. It is building from source and linking to the buggy Apple Accelerate library (instead of the OpenBLAS library we ship with our binary wheels. NumPy has a smoke test at import that Accelerate fails, so end-users are trying to install numpy, which is building from source, which does not work.
I think we tracked it down to a build problem where python3.9 from HomeBrew is not accepting the macosx_10_9_x86_64 platform tag. Since the NumPy wheels use that tag, python3.9 -m pip install numpy will scan available binary packages, not find a compatible one, and trigger a build from source, leading to the situation described above.
We tried hard to detect Accelerate in our build system but failed. Maybe you all have some good idea how to avoid using it?
xref numpy/numpy#17784.