Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v4: Use LOCATION Python FIND_STRATEGY #419

Merged
merged 1 commit into from
Jan 3, 2025

Conversation

mathomp4
Copy link
Member

@mathomp4 mathomp4 commented Jan 2, 2025

Tests at NAS have shown that using the VERSION find strategy for Python was causing an issue because there is a /usr/bin/python3.12 that is on the system PATH but it is "basic" and doesn't have f2py so our f2py bits were failing.

Using LOCATION tells it to use the Python we want (e.g., GEOSpyD)

@mathomp4 mathomp4 added the 0 diff The changes in this pull request have verified to be zero-diff with the target branch. label Jan 2, 2025
@mathomp4 mathomp4 self-assigned this Jan 2, 2025
@mathomp4 mathomp4 requested a review from a team as a code owner January 2, 2025 17:00
@mathomp4 mathomp4 merged commit 083180f into develop Jan 3, 2025
10 of 14 checks passed
@mathomp4 mathomp4 deleted the feature/mathomp4/v4-python-location branch January 3, 2025 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 diff The changes in this pull request have verified to be zero-diff with the target branch.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant