[SciPy-dev] NumPy f2py GSOC project
Fri Mar 27 01:32:20 CDT 2009
I have tried to contact Pearu but my schools mail server has bounced the
emails I send back for some reason. I'm going to try again tomorrow.
code clean-up/plan building is something that does interest me. I've seen a
few other mentor organizations that have 'bug fixer' ideas listed for gsoc
projects so I think I could sell a project like that. the way I'd see it
working is, I'd help clean-up code and bugfix for the first part of the
summer, to get acquainted with the various pieces to NumPy, then the later
portion would be starting to flesh out a plan for the transition. I'll see
what I can come up with for a proposal for this type of project.
I would like to continue working with the NumPy/SciPy team after this
summer. I think it's a bit of a waste, both for me and for the mentors, to
ditch a project after only a couple months. So I should be around when more
work is being done on the conversion.
2009/3/27 Charles R Harris <firstname.lastname@example.org>
> 2009/3/26 ross smith <email@example.com>
>> 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?
> I think the main things going on in numpy at this time are test
> coverage/documentation/code cleanup. David is also working the
> build/distribution problems. I can't speak for scipy, as I am less familiar
> with its current state.
> It would be a shame to waste your experience with the python 2.x -> 3.x
> transition. I wish I was in a better position to help plan out the project,
> but I don't even know what the problems will be at this point. Which
> probably doesn't help you pitch the project to Google. No doubt there is a
> lot of code cleanup in the python sections of numpy that would help with the
> transition, but I don't know what that would be either.
> My feeling is we won't be working much on the transition until next year
> sometime. It would certainly be nice to have a plan in place before we
> start, but I don't know if that sort of thing interests you or if you could
> sell it to Google. I think it would require a lot of your time just getting
> familiar with all the parts of numpy and that is quite a job in itself.
> I think f2py remains a possibility, but you will have to judge that. It
> would certainly help if Pearu were available to guide that work. And like
> many open source projects that just growed, I suspect f2py is rather
> complicated. Hence Pearu's start on a refactoring. Have you tried contacting
> Scipy-dev mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Scipy-dev