2009/5/20 Stéfan van der Walt <ste...@sun.ac.za>: > David Cournapeau also put a check in place so that the NumPy build > will break if we forget to update the API version again. > > So, while we can't change the releases of NumPy out there already, we > can at least ensure that this won't happen again.
OK, great -- thanks for th info. From reading David's comments in the earlier thread: David > - Backward compatibility means that you can build something against David > numpy version M, later update numpy to version N >M, and it still works. David > numpy 1.3.0 is backward compatible with 1.2.1 it looks like our best bet will be to build our python2.4 and python2.5 binaries against 1.2.1 and our python2.6 binaries against 1.3.0 (since there are no older python2.6 numpy builds on the sf site anyhow). I'll post on the mpl list and site that anyone using the new mpl installers needs to be on numpy 1.2.1 or later. JDH _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
