On Wed, Apr 22, 2009 at 1:01 PM, William Stein <[email protected]> wrote:
> 2009/4/21 Robert Bradshaw <[email protected]>:
>> On Apr 21, 2009, at 8:21 PM, Brian Granger wrote:
>>
>>>> Lets not count on doing so for now at least. There are license
>>>> considerations to consider too--f2py is GPL and as such wouldn't make
>>>> it into Python without relicensing.
>>>
>>> Mmmm, f2py ships with numpy and thus can't be GPL.  The home page of
>>> f2py lists is as LGPL.  Now whether or not that is sufficient for
>>> Python itself is another question.
>>
>> Yes, sorry, LGPL. In any case, lets treat it as an external
>> dependancy for now.
>
> 1. I think there is no way Python would ship LGPL'd code as part of
> standard Python.
>
> 2. That f2py ships with numpy doesn't imply that f2py isn't GPL
> (though it of course isn't GPL).

It indeed does not imply anything legally, but we would rather not
include any shipped code which is not BSD. I was actually very
surprised to learn that f2py was not BSD-like, and I checked the
sources of f2py as shipped in numpy: those are explicitly covered by
the Numpy license, as can be seen by numpy/f2py/docs/README.txt:

.. -*- rest -*-

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 F2PY: Fortran to Python interface generator
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

:Author: Pearu Peterson <[email protected]>
:License: NumPy License
:Web-site: http://cens.ioc.ee/projects/f2py2e/
:Discussions to: `f2py-users mailing list`_
:Documentation: `User's Guide`__, FAQ__
:Platforms: All
:Date: $Date: 2005/01/30 18:54:53 $

...

Davd
_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev

Reply via email to