> Python has many people working on it, but it's a lot simpler > in structure. It's fairly easy to work on things like adding > a new object or library module without fear of disturbing > anything else. > > The various parts of Pyrex are much more closely coupled than > that. I have to think long and hard before changing anything, > and I'm the one who wrote it.
We notice that in Cython too, and I've been thinking a lot about this aspect. If you haven't read it already I'd love to hear your comments some time on this thread: http://thread.gmane.org/gmane.comp.python.cython.devel/1384 (BTW my brain was on pause when I wrote the "stagnant part", I agree with Robert's correction). (Also rereading it again it is not completely clear in some parts, I apologize for this, just ask...) When I push for these changes, I don't want it to be taken as critisicm of your work -- the current structure seems to be proper for Pyrex, and was probably more ideal for launching a project like this too (Keep It Simple etc.). It's not as bad a structure as such, the problem is that it doesn't seem to scale up to the things we'd like to do with Cython, and the level of developer independence we need. > So I think it's probably a good thing having Cython as a > separate project where people are free to try out all their > wild ideas. Then when the dust has settled I can take the > best ideas and fold them back into Pyrex. I know that you talk mostly about ideas here, but a note about code: Some new features in Cython might be rather difficult to port over, because of the stuff in the thread above. (But probably these might be the features you're least interested in.) > directions rather different from Pyrex, such as turning > into a Python compiler, and/or a NumPy compiler, and folks > are rushing into making changes for py3k, when I've hardly > begun to think about what I want to do about that. As for NumPy, you might be right :-) the goal is pretty far from Pyrex' goal. I think that is a testimony to the ideas in Pyrex ... they are useful far outside of Pyrex' goals, and I'd like to build on that base for numerical computation use. However, I'll make sure there are no explicity references to NumPy within Cython, except that it might ship a "numpy.pxd" file; it's all about adding generic compiler features that's necesarry for such a pxd file and will also be useful for similar libraries. Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
