[SciPy-dev] NumPy f2py GSOC project
ross smith
rjsm@umich....
Thu Mar 26 23:54:37 CDT 2009
Yes I do. I can see the Numpy and Cython dependence, which may not be a
good idea but Cython can produce both python2 code and python3 code.
In any case, I'm seeing this project getting harder to pitch and define so,
are there any other projects for NumPy or SciPy that would appropriate for a
gsoc project?
-Ross
2009/3/27 Charles R Harris <charlesr.harris@gmail.com>
>
>
> 2009/3/26 ross smith <rjsm@umich.edu>
>
>> >What part will be ported to Cython? As I
>>
>> >understand it, a) f2py itself is entirely written in Python already, b)
>> >it generates a C module much like Cython does, which must currently be
>> >kept Py2 because of the NumPy dependency.
>>
>> the fortranobject is written in C, and would be ported to Cython. also,
>> much of the python code could be ported to cython for some speedup and to
>> make the code 'python neutral'. Cython would do the heavy lifting of
>> generating valid python (2 or 3) code when it is compiled, so the code
>> wouldn't have to be ported by hand when the rest of Numpy is ported.
>>
>
> So you intend for the output file to be in cython? I suppose the reasoning
> here is that that would solve c-level compatibility problems. I'm not sure
> that's the best way to go, it introduces a dependency on cython python3.0
> and numpy support and I don't know where that stands. Maybe Dag can comment.
> I don't think rewriting the parser itself in cython is a good idea.
>
> Chuck
>
>
>
> _______________________________________________
> Scipy-dev mailing list
> Scipy-dev@scipy.org
> http://mail.scipy.org/mailman/listinfo/scipy-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/scipy-dev/attachments/20090327/a0cff0b5/attachment.html
More information about the Scipy-dev
mailing list