[Numpy-discussion] numpy 2.0, what else to do?
Mon Feb 15 10:04:04 CST 2010
In the list of things to do, I suggest deleting completely the old
histogram behaviour and the `new` keyword.
The `new` keyword argument has raised a deprecation warning since 1.3
and was set for removal in 1.4.
On Mon, Feb 15, 2010 at 9:21 AM, Robert Kern <firstname.lastname@example.org> wrote:
> On Mon, Feb 15, 2010 at 05:24, David Cournapeau <email@example.com> wrote:
>> David Cournapeau wrote:
>>> It is always an ABI change, but is mostly backward compatible (which is
>>> neither the case of matplotlib or scipy AFAIK).
>> This sentence does not make any sense: I meant that it is backward
>> compatible from an ABI POV, unless the structure PyArray_Array itself is
>> included in another structure (instead of merely being used).
>> Neither matplotlib or scipy do that AFAIK - the main use-case for that
>> would be to inherit from numpy array at the C level, but I doubt many
>> extensions do that. For people who do C++, that's the same problem as
>> changing a base class, which always break the ABI,
> Actually, it's PyArray_Descr, which corresponds to numpy.dtype, that
> has been extended. That has even fewer possible use cases for
> subtyping. I know of none.
> Robert Kern
> "I have come to believe that the whole world is an enigma, a harmless
> enigma that is made terrible by our own mad attempt to interpret it as
> though it had an underlying truth."
> -- Umberto Eco
> NumPy-Discussion mailing list
More information about the NumPy-Discussion