On Thu, Dec 29, 2011 at 4:36 PM, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
On Thu, Dec 29, 2011 at 9:50 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
Hi All,
I thought I'd raise this topic just to get some ideas out there. At the moment I see two areas that I'd like to see addressed.
Documentation editor. This would involve looking at the generated documentation and it's organization/coverage as well such things as style and maybe reviewing stuff on the documentation site. This would be more technical writing than coding. Test coverage. There are a lot of areas of numpy that are not well tested as well as some tests that are still doc tests and should probably be updated. This is a substantial amount of work and would require some familiarity with numpy as well as a willingness to ping developers for clarification of some topics.
Thoughts?
First thought: very useful, but probably not GSOC topics by themselves.
For a very good student, I'd think topics like implementing NA bit masks or improved user-defined dtypes would be interesting. In SciPy there's also a lot to do, and that's probably a better project for students who prefer to work in Python.
Thanks for bringing this up. Last year we missed the boat, it would be good to get one or more slots this year.
Ralf
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Along with test coverage, have any of you considered any systematic monitoring of NumPy performance? With all of the extensive refactoring / work on the internals, it would be useful to keep an eye on things in case of any performance regressions. I mention this because I started a little prototype project (http://github.com/wesm/vbench) for doing exactly that for my own development purposes-- it's already proved extremely useful. Anyway, just a thought. I'm sure a motivated student could spend a whole summer writing unit tests for NumPy and nothing else. - Wes