Eric Firing wrote: > _backend_gdk.c and nxutils.c both call into the numpy C API; maybe some > c++ code does also. It is not entirely clear to me whether 1.1 is > sufficiently binary-compatible that this is safe. >
The C API did not change (with the possible exception of additions). I'd be really surprised if this is an issue -- the numpy devs worked to make sure there would be no breakage at the C API level. (And even if it did change, as it might one day in the future -- numpy 2? -- there's a check that happens at numpy load time, during import_array(), that checks whether the version of numpy you compiled with is the version you're loading now and raises an exception if it's not. So, the old nightmares of numeric and numarray possibly being run against binary incompatible versions are a thing of the past. This check actually saved quite a few headaches during the runup to numpy 1.0, when there were a number of C API changes happening in quick succession as Travis worked to get it right. That machinery is still in there.) ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
