David Cournapeau wrote: > On Sun, Jan 24, 2010 at 10:55 PM, Stefan Behnel <[email protected]> wrote: > >> David Cournapeau, 24.01.2010 14:16: >> >>> On Sat, Jan 23, 2010 at 4:38 AM, Robert Bradshaw >>> <[email protected]> wrote: >>> >>>> Up at >>>> http://sage.math.washington.edu/home/robertwb/cython/Cython-0.12.1.alpha0.tar.gz >>>> . I just packaged up the current cython-devel tip, will start a Sage >>>> building with it later today. >>>> >>> It seems that it is being taken care of, but I would like to confirm: >>> will the type checking done by cython be relaxed for this release ? >>> >> I assume you are referring to the extension type size checking when >> cimporting between modules? >> > > Yes - currently, numpy 1.4.0 is not compatible with scipy 0.7.1 > binaries (at least) because of this. I would like to release 1.4.1 and > scipy 0.7.1.1 ASAP, as it is a rather major inconvenience to people > relying on binaries, > I don't think there's anything you can do in NumPy or SciPy (unless those contained Cython sources?) Basically people's Cython extensions must be recompiled with Cython 0.12.1; the NumPy/SciPy release has little to do with it.
(Unless you actually refrained from breaking binary compatability in 1.4.0 because of Cython?) It certainly looks like http://hg.cython.org/cython-devel/rev/9d8b2ecef24a should have taken care of it; of course it would be good to have somebody verify that it indeed solves the exact issue with NumPy (if Robert didn't already). This certainly can be made more friendly -- I'd like to have a decorator that could be used on the NumPy classes (so that there's no warning either), and introduce an __onpxdimport__ function which could be used in numpy.pxd to make sure import_array is always called (so that NumPy will always use its own versioning scheme). I may very well not get time for before the release though. Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
