In the end all we need to get passing builds was to restrict numpy. I guess it seems premature to change the pyroject.toml build requirements, but I'm not sure I fully understand how that all works.
This should also fix #1596 . As @emlys mentioned, I observed that conda-forge did not install the latest PyInstaller release, and I think it could be due to the fact that we are stuck on macos-13 rather than macos-latest (see #1586 ).
Using pip to install PyInstaller worked around that problem, maybe because pip does less in the way of version-solving?
Similarly, pygeoprocessing is a "pip-only" install for us, and that is the only way we're able to solve the Python 3.12 environment at the moment.
Fixes #1606
Checklist
[ ] Updated HISTORY.rst and link to any relevant issue (if these changes are user-facing)
In the end all we need to get passing builds was to restrict numpy. I guess it seems premature to change the
pyroject.tomlbuild requirements, but I'm not sure I fully understand how that all works.This should also fix #1596 . As @emlys mentioned, I observed that
conda-forgedid not install the latest PyInstaller release, and I think it could be due to the fact that we are stuck onmacos-13rather thanmacos-latest(see #1586 ).Using
pipto install PyInstaller worked around that problem, maybe because pip does less in the way of version-solving?Similarly,
pygeoprocessingis a "pip-only" install for us, and that is the only way we're able to solve the Python 3.12 environment at the moment.Fixes #1606
Checklist