[Numpy-discussion] numpy 2.0, what else to do?

David Cournapeau david@silveregg.co...
Mon Feb 15 04:42:54 CST 2010


Sebastian Haase wrote:
> On Mon, Feb 15, 2010 at 11:17 AM, Francesc Alted <faltet@pytables.org> wrote:
>> A Sunday 14 February 2010 13:40:17 Stéfan van der Walt escrigué:
>>> On 14 February 2010 01:23, David Cournapeau <cournape@gmail.com> wrote:
>>>> I think that there should be absolutely no change whatsoever, for two
>>>> reasons: - the release is in a few weeks, it is too late to change much.
>>>> The whole datetime issue happened because the change came too late, I
>>>> would hope that we avoid the same mistake.
>>> I agree with David; we should not rush to include any new, untested
>>> features now.  That is what 2.1 is for.
>> +1
>>
>> As Travis pointed out, NumPy 2.0 should mostly be a release to contain all the
>> ABI changes we think we will need until NumPy 3.0 (hope that David and the
>> other core developers can figure out a good way to do this).
>>
>>> To quote an old war poster, let's "keep calm and carry on."
>> Exactly :-)
>>
>> --
> Is the addition of a dict-attribute (or just a pointer to one) an ABI change ?

It is always an ABI change, but is mostly backward compatible (which is 
neither the case of matplotlib or scipy AFAIK). But ABI changes for 2.0 
are OK, that's the whole point of doing it in the first place.

cheers,

David


More information about the NumPy-Discussion mailing list