[SciPy-dev] Numpy/Scipy GSOC project(s)
Mon Mar 30 03:36:34 CDT 2009
I apologize for my lack of response on this, I have a lot due in my classes
so I was focusing on my schoolwork.
On Fri, Mar 27, 2009 at 04:13, David Cournapeau <
> ross smith wrote:
> > 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.
> Which email address did you use ? My impression is that Pearu still
> partcipates in the numpy/scipy mailing lists.
I've tried email@example.com , the issue has and is that my schools mail
server is rejecting my outbound emails.
> If you are interested in working on scipy-related projects, something
> which could help the transition is to replace C code by cython. This
> would be particularly helpful in scipy - there are many modules which
> are crufty and would benefit from code cleaning, but if you don't know
> cython, maybe that's not something that interesting for you. Cython is
> not difficult to use, though. scipy.signal comes to mind, to take
> something where I could definitely help you - but there are other
> modules as well, where other people would be more qualified
> (scipy.ndimage, etc...). at least in the
> case of scipy.signal, there is definitely some new features which are
> needed as well (new feature is generally more fun than code cleanup/bug
> hunting). Of course, you should choose modules which interest you.
scipy.signal sounds very interesting to me. I've been toying with the idea
of a soft-synth written in python for a while now. I would be up for
tidying up that module. what other features would be of use to implement?
>One module means that it would be easier for
>you to work on, easier for use to help/coordinate
After looking at how much code is in a single module, I wholeheartedly
I'm planning on hedging my bets a bit on the GSOC applications. I can
submit up to 20 applications. I'm going to write up one for a 'preliminary
toward Numpy for py3k' and one for 'clean up and add XXXX to
> As a start, what would be extremely useful is to be able to build
>Cython ufuncs on the fly.
This also sounds like something very useful that I'd be interested in.
right at the moment, I'm a bit unsure on the details of how to implement
this or where.
as always, feedback and ideas are welcome.
thanks for your input thus far!
> And if you become a regular numpy/scipy contributor, you will be able to
> help for the transition later anyway.
> Scipy-dev mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Scipy-dev