[Numpy-discussion] [REVIEW] Update NumPy API format to support updates that don't break binary compatibility

Andrew Straw strawman@astraw....
Sat Aug 16 02:21:35 CDT 2008


Looking at the code, but not testing it -- this looks fine to me. (I 
wrote the original NPY_VERSION stuff and sent it to Travis, who modified 
and included it.)

I have added a couple of extremely minor points to the code review tool 
-- as much as a chance to play with the tool as to comment on the code.

-Andrew

Stéfan van der Walt wrote:
> The current NumPy API number, stored as NPY_VERSION in the header files, needs
> to be incremented every time the NumPy C-API changes.  The counter tells
> developers with exactly which revision of the API they are dealing.  NumPy does
> some checking to make sure that it does not run against an old version of the
> API.  Currently, we have no way of distinguishing between changes that break
> binary compatibility and those that don't.
>
> The proposed fix breaks the version number up into two counters -- one that gets
> increased when binary compatibility is broken, and another when the API is
> changed without breaking compatibility.
>
> Backward compatibility with packages such as Matplotlib is maintained by
> renaming NPY_VERSION to NPY_BINARY_VERSION.
>
> Please review the proposed change at http://codereview.appspot.com/2946
>
> Regards
> Stéfan
> _______________________________________________
> Numpy-discussion mailing list
> Numpy-discussion@scipy.org
> http://projects.scipy.org/mailman/listinfo/numpy-discussion
>   



More information about the Numpy-discussion mailing list