On Fri, Jul 2, 2010 at 7:58 AM, Russell Reagan <[email protected]> wrote: > I am curious, in what ways does Cython not meet your needs?
Same here. Seems like for a game, though, much of the heaving lifting would be done by the underlying graphics modules (e.g. OpenGL on a GPU). > I think it > would be beneficial to know, in order to identify areas which Cython > needs to be improved in order to be more useful in real world projects. +1 > I have not done a great deal of work in Cython yet, but my perception > is that with Cython, you should be able to write in Python, modify the > Python with augmenting .pxd files, and get close to the equivalent > speed of C code. > > So I am curious if: > > 1. My theoretical view of Cython is flawed. Or... Your understanding is right on. > 2. Practice currently has not caught up to theory. Or... There's still some work to do, but it's already the case for most numerical things (of course we could always make thing easier) and many other usecases as well. (The speed advantages of Cython for non-numerical things are not usually in the 100-1000x, mostly reflective of the fact that the speed disadvantages of Python vs. C are not as extreem in this case.) > 3. Cython is not intended to address your specific situation, and I > have misunderstood your intentions and goals. Cython is used to make specific pieces of code fast, not speed up the entire interpreter (though one could presumably compile anything one is interested in). - Robert _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
