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

[Sean Farley]

Joshua Root  writes:

> On 2016-1-15 05:51 , Sean Farley wrote:
>> 
>> Joshua Root  writes:
>> 
 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.
>> 
>> No, it is not optional. Trying running 'numpy.test()'. Or try compiling
>> with 'atlas +nofortran'. Not having fortran will generate a broken numpy
>> library.
>> 
>> Side note: We should consider getting rid of 'atlas +nofortran'. I
>> haven't found a port that depends on atlas but works without fortran.
>
> What you're saying is that to use fortran with numpy you need to enable
> its fortran support. Well, yes.
>
> If you're just using, say, pyopengl, then no, you don't need fortran
> support.

While a project *might* not need numpy's fortran, numpy expects a
fortran compiler:

"you’ll also need a FORTRAN 77 compiler installed." [1]

This means any dependent of numpy is correct in assuming that the python
compiler wrappers that numpy provide will have fortran. The amount of
headache this solves for us, I believe, far outweighs not having
fortran.

Until we can reliably depend on variants, I don't want a broken numpy
library installed (same with my feelings of removing atlas +nofortran).
It just causes too much headache.

[1] http://docs.scipy.org/doc/numpy-1.10.1/user/install.html
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

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

[Joshua Root]

On 2016-1-16 05:54 , Sean Farley wrote:
> 
> Joshua Root  writes:
> 
>> On 2016-1-15 05:51 , Sean Farley wrote:
>>>
>>> Joshua Root  writes:
>>>
> 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.
>>>
>>> No, it is not optional. Trying running 'numpy.test()'. Or try compiling
>>> with 'atlas +nofortran'. Not having fortran will generate a broken numpy
>>> library.
>>>
>>> Side note: We should consider getting rid of 'atlas +nofortran'. I
>>> haven't found a port that depends on atlas but works without fortran.
>>
>> What you're saying is that to use fortran with numpy you need to enable
>> its fortran support. Well, yes.
>>
>> If you're just using, say, pyopengl, then no, you don't need fortran
>> support.
> 
> While a project *might* not need numpy's fortran, numpy expects a
> fortran compiler:
> 
> "you’ll also need a FORTRAN 77 compiler installed." [1]
> 
> This means any dependent of numpy is correct in assuming that the python
> compiler wrappers that numpy provide will have fortran. The amount of
> headache this solves for us, I believe, far outweighs not having
> fortran.
> 
> Until we can reliably depend on variants, I don't want a broken numpy
> library installed (same with my feelings of removing atlas +nofortran).
> It just causes too much headache.
> 
> [1] http://docs.scipy.org/doc/numpy-1.10.1/user/install.html

Installing all of gcc when you don't need it is a bit of a headache too.
Whatever, I can just revert this locally, though I would guess there are
other users in the same position.

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [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
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

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

[Joshua Root]

On 2016-1-15 05:51 , Sean Farley wrote:
> 
> Joshua Root  writes:
> 
>>> 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.
> 
> No, it is not optional. Trying running 'numpy.test()'. Or try compiling
> with 'atlas +nofortran'. Not having fortran will generate a broken numpy
> library.
> 
> Side note: We should consider getting rid of 'atlas +nofortran'. I
> haven't found a port that depends on atlas but works without fortran.

What you're saying is that to use fortran with numpy you need to enable
its fortran support. Well, yes.

If you're just using, say, pyopengl, then no, you don't need fortran
support.

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

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

[Sean Farley]

Joshua Root  writes:

>> 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.

No, it is not optional. Trying running 'numpy.test()'. Or try compiling
with 'atlas +nofortran'. Not having fortran will generate a broken numpy
library.

Side note: We should consider getting rid of 'atlas +nofortran'. I
haven't found a port that depends on atlas but works without fortran.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

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

[Joshua Root]

> 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.

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev