Sebastien Binet wrote: > On Wednesday 26 August 2009 21:44:04 Dag Sverre Seljebotn wrote: >> Dag Sverre Seljebotn wrote: >>> As many of you know me and Kurt attended SciPy 09. Four Cython-related >>> events were held: >>> >>> - An introductory tutorial to Cython (by me) >>> - A talk about Cython for numerics (by me again) >>> - A talk on Fwrap (by Kurt) >>> - A Cython BoF >>> >>> You can find links to slides and videos for the three first on >>> http://conference.scipy.org. >>> >>> An intensive week like that makes me reflect on what Cython is good >>> about, lacking, etc. etc. >>> >>> First of all, there seems to be quite a lot of interest in Cython, many >>> thinks it is excellent, and many thanked me personally for our efforts. >> One other thought from SciPy 09: It emphasised to me that one of the >> most important things missing in Cython, perhaps more than any single >> feature, is solid, updated introductory-level documentation. >> (docs.cython.org is more of a reference...) > and probably a howto for developers: cython's citymap, the 10,000 ft view of > the overall organization of cython's code, the various concepts, etc... > > right now I have just been playing on the shore w/o the ability (nor the > time, > to be frank) to play further with the code.
I'm not too sure about this. It's always a question whether the investment is worth it. I have a strong feeling that developing on Cython will for the foreseeable future happen through mentoring. Trying to upfront come up with all the potential questions one might ask about the code base, or just writing down the 10 000 ft organization of the code, is very time consuming. (Especially since Cython's code organization isn't the nicest -- but I'd rather spend time to very gradually fix that than to document it...) So: When you get the time to contribute to Cython, just state what you are interested in fixing, and the existing developers will come along and tell you what you need to know. There's been several threads on the mailing list that's basically "how to fix this bug" (over the summer I mentored Kurt over Skype which worked out excellently.) Perhaps we should state just that somewhere visible though. (BTW, for anyone reading this, a nice, rather low-hanging fruit right now is just to write testcases for pyximport and merge in the existing patches for it.) -- Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
