BLD: only install the f2py command, not f2py3 or f2py3.X
#24235
Conversation
Also extend a comment on linking libm, and clean up a few lines of unused code.
Addresses a task in numpygh-23981.
This takes care of an open issue from the Meson build migration (xref numpygh-23981). Use of `f2py3` is not present at all in the docs, and Python 2.7 is well and truly gone now. Using `f2py3.11` or similar is even less common, difficult to support (it prevents keeping the metadata in `pyproject.toml` completely static), and it's perfectly fine in those cases anyway to use `python3.11 -m numpy.f2py`. Going via a specific Python interpreter executable has become more commonplace, e.g. `python -m pip` to ensure picking up the correct version of `pip`.
rgommers
added
36 - Build
I think it should be documented as the preferred way. Like pip, there is always the problem of which numpy is being used, which can a problem when there are multiple installations. |
|
Does f2py actually produce different results based on the python version it is running under, even for python2 vs python3? Or does it only change depending on the numpy version (which makes sense, different versions of f2py will naturally tend to produce different results)? If anything, maybe there should be a ... The original rationale in f22a33b appears to have been "because linux distros" which seems misguided as Linux distros should just be shipping a single entrypoint anyway for command-line programs. When they break this theme it causes issues such as "there is no cython command on Debian because the python2-cython package was deleted"... |
Not for transpiling to C/Fortran wrappers only, but
Agreed. I think a single |
3 participants
Also fix a build warning for a missing
checkkeyword in arun_commandcall, and some other build file cleanups.This takes care of an open issue from the Meson build migration (xref gh-23981).
Use of
f2py3is not present at all in the docs, and Python 2.7 is well and truly gone now. Usingf2py3.11or similar is even less common, difficult to support (it prevents keeping the metadata inpyproject.tomlcompletely static), and it's perfectly fine in those cases anyway to usepython3.11 -m numpy.f2py.Going via a specific Python interpreter executable has become more commonplace, e.g.
python -m pipto ensure picking up the correct version ofpip.