Hi all.
I'd like to make the proposition of devoting myself over the next few
days to updating the documentation for cython... completely.
So what I ask in return are answers to questions I will have and for
all of you to blurt out, in this thread, anything you can possibly
think of that might be of interest to a "well oiled" set of
documentation. I will put a lot of thought and detail into how it will
be perceived and digested by both the casual and technical users.
If we also need to enhance tools like sphinx/pygments, etc., I'll be
glad to tackle that as well.
Right off the bat, off of the top of my head, I'd like to clarify
Cython's ability at this point...
1) We need to establish for users Cython's current state of
capability. Cython's "under the hood" ability to digest
meta-programming is an enigma to the uniformed user. For example, A
question I constantly ask my-self.. "Is that optimized to C code or am
I still dealing with the Python code". Do I need to use C-API calls or
not. Like for instance if I use the {} operator set.. is it still
endowed with python overhead, or is current cython magic able optimize
it.
2) I'm a numbers guy. I really need to know exactly where we stand
with numpy and the buffer interface. Particularly, with structured
array's.
3) What Is currently on the functionality-implementation agenda. What
is Cython's road map for say, the next six months.
4) Come to think of it.. I think it would be cool to highlight
Cython's "Google Summer of Code" participants and their contributions.
5) etc.. etc..
So, lay it on me and I will do what it takes to make Cython's
documentation shine. I'm a big advocate of thoughtful documentation
you see.. considering OSS is entirely how I've learned what I do know
about computer science.
Peter
_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev
