v3: Use LOCATION Python FIND_STRATEGY
This update to v3 moves to use the LOCATION
strategy for finding Python. This is needed as NAS (at least) has a very recent, but empty (no f2py
) Python stack in the default path. Using LOCATION
should limit it to the Python we want (e.g., via GEOSpyD module)
From CHANGELOG.md
Changed
- Move to use Python
FIND_STRATEGY LOCATION
by default. This is needed as NAS (at least) has a very recent, but empty (no f2py) Python stack in the default path. UsingLOCATION
should limit it to the Python we want (e.g., via GEOSpyD module)
What's Changed
Full Changelog: v3.55.0...v3.56.0