This is off-topic and should be directed to the pyrex/cython list, but since we're on the subject: I suppose the following is true, but let me ask, since I have not used Cython. Please correct me if I'm wrong. I have a bunch of pyrex compiled .pyx code. If I start adding some Cython compiled code, all the extensions will live happily without colliding, even if I don't re-compile my old .pyx files with Cython. (I can't imagine how they'd conflict, since they both translate to .c extensions without anything to collide. Or are there linker-level symbols that collide or something difficult?) -Andrew Fernando Perez wrote:
On Tue, Apr 8, 2008 at 4:38 PM, Travis E. Oliphant
wrote: I say just add it. We should move forward with Cython. More important is to see if random actually builds with Cython right now. There was an issue that I recall from a few weeks ago that Cython could not build the pyrex extension in NumPy.
OK, I'll play with random for a bit.
BTW, the original 'bug' that started this thread is due to a change in Cython's casting behavior explained here:
http://wiki.cython.org/DifferencesFromPyrex
it's fixed with a simple extra (void *) cast as shown here:
print 'Printing array info for ndarray at 0x%0lx'% \ (
arr,) I just committed that code to the bzr branch.
In summary:
1. Do you want me to obliterate the old numpy/doc/pyrex and replace it with numpy/doc/cython? That would make it clear what the tool to use is...
2. I'll work on random and report shortly.
Cheers,
f _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion