[Numpy-discussion] python-numpy debian package and f2py

Pearu Peterson pearu@cens.ioc...
Mon Dec 3 04:22:51 CST 2007


Some additional notes:

- note that f2py in numpy and in python-f2py are *different*
tools and therefore python-f2py should not be considered
depreciated more than python-numeric is. So, python-f2py
should stay provided python-numeric is there. It might be
appropiate to rename python-f2py to python-f2py2e.

- the conflict between f2py scripts can be easily resolved
by renaming f2py script in python-f2py package to, say,
f2py2e (that would be an simple change in f2py2e/setup.py file).
The f2py script in numpy has --2d-numeric switch
that when used would import f2py2e package instead of numpy.f2py.

Pearu

On Mon, December 3, 2007 10:20 am, Pearu Peterson wrote:
> Ho,
>
> f2py is part of numpy and therefore there is no need to
> have python-f2py package. The version number of f2py
> (2_3816, for instance), indicates which SVN commit changed
> the f2py package and has local usage only.
>
> python-f2py package could be retained only for backward
> compatibilty for users who are importing f2py2e package
> and for users who need Numeric and numarray support in f2py.
> Otherwise there is no need for it.
>
> Note that if debian is going to ship Numeric then it should
> also ship python-f2py. But this means that one cannot
> install numpy as the will be a conflict of f2py scripts.
>
> Regards,
> Pearu
>
> On Mon, December 3, 2007 2:52 am, Ondrej Certik wrote:
>> Hi,
>>
>> I am a comaintainer of the python-scipy package in Debian and now it
>> seems to be in quite a good shape. However, the python-numpy package
>> is quite a mess, so as it usually goes in opensource, I got fedup and
>> I tried to clean it. But I noticed, that f2py was moved from external
>> package into numpy, however
>> the versions mishmatch:
>>
>> The newest (deprecated) python-f2py package in Debian has a version
>> 2.45.241+1926, so I assume this was the version of f2py, before
>> merging
>> with numpy. However, the f2py in numpy says when executing:
>>
>> Version:     2_3816
>> numpy Version: 1.0.3
>>
>> so I assume the version of f2py in numpy is 2_3816? So has the
>> versioning scheme of f2py changed? Another question - since both numpy
>> and f2py
>> is now built from the same source, doesn't f2py simply has the same
>> version as numpy, i.e. 1.0.3?  Note: I know there is a newer numpy
>> release, but that's
>> not the point now.
>>
>> I am asking because we probably will have to remove the old
>> python-f2py package and build a new one from the sources of numpy,
>> etc., and it will
>> take some time until this happens (ftpmasters need to remove the old
>> package from the archive, then the new binary package needs to go to
>> the
>> NEW queue for approval etc.), so I would like to make sure I
>> understand the versioning and the future plans with numpy and f2py,
>> before starting
>> the transition in Debian.
>>
>> Actually, does it even make sense to create a python-f2py package? It
>> seems so (to me), it's a separate program. But since you decided to
>> merge it
>> with numpy, what are your thoughts about it?
>>
>> Thanks a lot,
>> Ondrej
>> _______________________________________________
>> Numpy-discussion mailing list
>> Numpy-discussion@scipy.org
>> http://projects.scipy.org/mailman/listinfo/numpy-discussion
>>
>
>
> _______________________________________________
> Numpy-discussion mailing list
> Numpy-discussion@scipy.org
> http://projects.scipy.org/mailman/listinfo/numpy-discussion
>




More information about the Numpy-discussion mailing list