v4: Fixes to allow for odd Python setups and f2py#428
Merged
Conversation
mathomp4
added
the
0 diff
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR to v4 is an attempt to let f2py work in odd scenarios where perhaps more than one Python stack is in the PATH. In some cases, this is expected (Spack) but in other cases, it is an unsupported way forward (two different Miniforge stacks of different Python vintage).
First, we look for bare
f2pyfirst as systems like Spack only install that.Second, we look to see if the Python executable is the same path as the f2py found. If not, we add a
WARNINGto the CMake output. We cannotFATAL_ERRORbecause of things like Spack.This is about as good as we can do.
We also add an ugly hack for f2py on macOS with AppleClang because meson and CC and I don't know anymore.