f2py: request for help

Rainer Müller raimue at macports.org
Thu Oct 29 09:55:29 PDT 2015


On 2015-10-29 17:38, Mojca Miklavec wrote:
> On Thu, Oct 29, 2015 at 5:28 PM, Rainer Müller <raimue at macports.org> wrote:
>> On 2015-10-28 20:20, Mojca Miklavec wrote:
>>> Apart from the fact that I don't know how to get a binary called
>>> "f2py" (it would be nice to have the executable without the extension
>>> available), running
>>>     f2py-3.5 -c fib1.f -m fib1
>>> fails to find the Fortran compiler as it looks for gfortran only.
>>
>> Clear the option that controls the addition of the suffix:
>>
>> python.link_binaries_suffix
> 
> Then 2.7, 3.4 and 3.5 will all try to create the same binary, f2py.

Ah, well, I did not understand this is part of NumPy.

> What we need is probably some "port select" option, but then again
> f2py should probably be "compatible" with the version of python that
> has already been selected with "port select python". I have no clue
> how to achieve that. Port select python could not create a f2py
> symlink as that one comes from numpy.

In the way we treat python software, a port is meant to either:

a) provides a python module (with pyXY-* subports)
b) provides a standalone tool (with optional +pythonXY variants)

In this case, py-numpy provides both modules and tools, so the outcome
is not ideal. You end up with the suffixed tools as multiple pyXY-numpy
ports can be installed at the same time for different python versions.

Other ports such as ipython, pyflakes, pylint provide their own select
files.

Rainer


More information about the macports-dev mailing list