Trouble installing with pip due to scipy requirement

[hardsnow-sandia]

I attempted to install on an M2 macbook by running pip install . (trying to use setup.py), and it chokes when trying to install scipy. Editing setup.py to change scipy==1.11 to scipy fixes this particular issue.

For good measure, here's a snippet of what I get when running pip install . from the project using the as-is setup.py:

  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [43 lines of output]
      + meson setup /private/var/folders/ts/d2ynpwy126g8fnltrph4v4300042sk/T/pip-install-vkp4oagk/scipy_235f11729df1492a9e2d7d9feb125ecf /private/var/folders/ts/d2ynpwy126g8fnltrph4v4300042sk/T/pip-install-vkp4oagk/scipy_235f11729df1492a9e2d7d9feb125ecf/.mesonpy-euetnsf8/build -Dbuildtype=release -Db_ndebug=if-release -Db_vscrt=md --native-file=/private/var/folders/ts/d2ynpwy126g8fnltrph4v4300042sk/T/pip-install-vkp4oagk/scipy_235f11729df1492a9e2d7d9feb125ecf/.mesonpy-euetnsf8/build/meson-python-native-file.ini
      The Meson build system
      Version: 1.4.0
      Source dir: /private/var/folders/ts/d2ynpwy126g8fnltrph4v4300042sk/T/pip-install-vkp4oagk/scipy_235f11729df1492a9e2d7d9feb125ecf
      Build dir: /private/var/folders/ts/d2ynpwy126g8fnltrph4v4300042sk/T/pip-install-vkp4oagk/scipy_235f11729df1492a9e2d7d9feb125ecf/.mesonpy-euetnsf8/build
      Build type: native build
      Project name: SciPy
      Project version: 1.11.0
      C compiler for the host machine: cc (clang 15.0.0 "Apple clang version 15.0.0 (clang-1500.3.9.4)")
      C linker for the host machine: cc ld64 1053.12
      C++ compiler for the host machine: c++ (clang 15.0.0 "Apple clang version 15.0.0 (clang-1500.3.9.4)")
      C++ linker for the host machine: c++ ld64 1053.12
      Cython compiler for the host machine: cython (cython 0.29.37)
      Host machine cpu family: aarch64
      Host machine cpu: aarch64
      Program python found: YES (/Users/tredwar/anaconda3/envs/gtep-dev/bin/python3.12)
      Found pkg-config: YES (/opt/homebrew/bin/pkg-config) 0.29.2
      Run-time dependency python found: YES 3.12
      Program cython found: YES (/private/var/folders/ts/d2ynpwy126g8fnltrph4v4300042sk/T/pip-build-env-8bl59ozz/overlay/bin/cython)
      Compiler for C supports arguments -Wno-unused-but-set-variable: YES
      Compiler for C supports arguments -Wno-unused-function: YES
      Compiler for C supports arguments -Wno-conversion: YES
      Compiler for C supports arguments -Wno-misleading-indentation: YES
      Library m found: YES
      Fortran compiler for the host machine: gfortran (gcc 13.2.0 "GNU Fortran (Homebrew GCC 13.2.0) 13.2.0")
      Fortran linker for the host machine: gfortran ld64 1053.12
      Compiler for Fortran supports arguments -Wno-conversion: YES
      Checking if "-Wl,--version-script" : links: NO
      Program pythran found: YES (/private/var/folders/ts/d2ynpwy126g8fnltrph4v4300042sk/T/pip-build-env-8bl59ozz/overlay/bin/pythran)
      Did not find CMake 'cmake'
      Found CMake: NO
      Run-time dependency xsimd found: NO (tried pkgconfig, framework and cmake)
      Run-time dependency threads found: YES
      Library npymath found: YES
      Library npyrandom found: YES
      pybind11-config found: YES (/private/var/folders/ts/d2ynpwy126g8fnltrph4v4300042sk/T/pip-build-env-8bl59ozz/overlay/bin/pybind11-config) 2.10.4
      Run-time dependency pybind11 found: YES 2.10.4
      Run-time dependency openblas found: NO (tried pkgconfig, framework and cmake)
      Run-time dependency openblas found: NO (tried pkgconfig and framework)
      
      ../../scipy/meson.build:159:9: ERROR: Dependency "OpenBLAS" not found, tried pkgconfig and framework
      
      A full log can be found at /private/var/folders/ts/d2ynpwy126g8fnltrph4v4300042sk/T/pip-install-vkp4oagk/scipy_235f11729df1492a9e2d7d9feb125ecf/.mesonpy-euetnsf8/build/meson-logs/meson-log.txt
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.