[144621] trunk/dports/python/py-numpy/Portfile

[Michael Dickens]

On Thu, Jan 14, 2016, at 02:43 AM, Joshua Root wrote:
> > Revision: 144621
> >           https://trac.macports.org/changeset/144621
> > Author:   sean at macports.org
> > Date:     2016-01-13 23:29:24 -0800 (Wed, 13 Jan 2016)
> > Log Message:
> > -----------
> > py-numpy: numpy needs fortran, so require it
> 
> We've been through this before; numpy does not need fortran, its fortran support is optional.

Well ... not exactly; or, not clear to me. With the prior NumPy, if you
do:

{{{
/opt/local/bin/python2.7 -c "import numpy; numpy.test()"
}}}

then it goes through it's various tests & eventually errors out with:

{{{
======================================================================
FAIL: test_scripts.test_f2py
----------------------------------------------------------------------
Traceback (most recent call last):
  File
  "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/case.py",
  line 197, in runTest
    self.test(*self.arg)
  File
  "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/testing/decorators.py",
  line 146, in skipper_func
    return f(*args, **kwargs)
  File
  "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/tests/test_scripts.py",
  line 82, in test_f2py
    assert_(success, "Warning: neither %s nor %s found in path" %
    f2py_cmds)
  File
  "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/testing/utils.py",
  line 53, in assert_
    raise AssertionError(smsg)
AssertionError: Warning: neither f2py nor f2py found in path

----------------------------------------------------------------------
Ran 5576 tests in 86.597s

FAILED (KNOWNFAIL=3, SKIP=9, failures=1)
}}}

I don't know where "f2py" is created, but it seems likely that it's
by/within NumPy. I get the same result whether I use the "old" NumPy
(before this change), or the "new" one. Whether with +gfortran or
without. Although f2py does not itself require a Fortran compiler, I'd
bet that once the conversion is done a Fortran compiler is used to
compile the code -- and, hence, Fortran really is required.

That said, I haven't tried to track down where this issue actually lies.
I think there's a ticket on this matter, too. HTH. - MLD