[Numpy-discussion] Memory order of array copies

Gael Varoquaux gael.varoquaux@normalesup....
Sun Sep 30 13:22:59 CDT 2012


On Sun, Sep 30, 2012 at 07:17:42PM +0100, Nathaniel Smith wrote:
> Is there anything better to do than simply revert np.copy() to its
> traditional behaviour and accept that np.copy(a) and a.copy() will
> continue to have different semantics indefinitely?

Have np.copy take an 'order=None', which would translate to 'K'. Detect
'None' as a sentinel that order as not been specified. If the order is
not specified, raise a FutureWarning that np.copy will change semantics
in 2 releases. In two releases, do the change.

That's how I would deal with it.


More information about the NumPy-Discussion mailing list