[SciPy-dev] NumPy f2py GSOC project

David Huard david.huard@gmail....
Thu Mar 26 12:51:03 CDT 2009


Ross,

I still don't understand how you'll test the py3k version of f2py if numpy
is not ported first ? I would have thought the first step in porting numpy
would be to port the ndarray type and its methods. But maybe that's already
too ambitious for a gsoc ?

Cheers,

David




2009/3/26 ross smith <rjsm@umich.edu>

> Hello,
>
> I've done some looking at what will be required for the project.
>
>
> 1.  port f2py to Cython (Py3k).
>     a. begin porting the C code to python, without worrying about
> speed-ups.  Instead focusing on proper runtime behavior
>     b. ask community to help with providing fortran code to test proper
> runtime behavior.
>     c. develop small test suit of fortran/python code for problem cases.
>     d. Fix major bugs introduced from porting.
>     e. Document code, (docstrings)
>     f. Beginning modifying code for speedier execution
>
> Midterm eval:
>     a.  Have f2py code all ported to Cython and compiling.
>     b.  Have at least 5 tests written and working in ported code.
> Final Eval
>    a.  Major bugs found during the summer squashed.
>    b.  f2py compiling and running as expected  for all test cases.
>    c.  Documentation completed for Cython code.
>
>
> I'd happily stay on to bugfix once the summer is done.  I'd still be a
> student so my availability would be limited at times.
>
> Comments ans Suggestions, as always, are welcome.
>
>
> -Ross
>
> _______________________________________________
> 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/20090326/2cac0c97/attachment.html 


More information about the Scipy-dev mailing list