[Numpy-discussion] [SciPy-user] Managing Python with NumPy and many external libraries on multiple Windows machines

Charles R Harris charlesr.harris@gmail....
Tue Apr 28 13:43:19 CDT 2009

2009/4/28 Stéfan van der Walt <stefan@sun.ac.za>

> 2009/4/28 David Cournapeau <cournape@gmail.com>:
> > the header file is not very reliable. More generally, I think we
> > should have a way to track C API and ABI relatively to the number
> > version, as well as automatically generate the related documentation.
> We can already do this: simply choose a convention for NPY_VERSION and
> NPY_FEATURE_VERSION so that they are related.

NPY_VERSION has been 0x01000009 since 1.0. NPY_FEATURE_VERSION was added for
1.2, but is useless since it can't be obtained through the API. I suggest we
keep only NPY_VERSION but split it into two parts, the upper 16 bits for ABI
changes that require extensions to be recompiled, and the lower 16 bits for
API changes that are backward compatible, so that the next release should
have version 0x0100000A. What to do with the current release is another
question. If we change the version for a bugfix release it won't be
compatible with 1.3.0. Hmm...

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/numpy-discussion/attachments/20090428/c98052d3/attachment.html 

More information about the Numpy-discussion mailing list