8000 np.copy should have order='K' by default for backward compatibility · Issue #469 · numpy/numpy · GitHub
[go: up one dir, main page]

Skip to content
np.copy should have order='K' by default for backward compatibility #469
Closed
@GaelVaroquaux

Description

@GaelVaroquaux

In current tree:

>>> a = np.ones((10, 10))
>>> np.copy(a.T).flags
  C_CONTIGUOUS : True
  F_CONTIGUOUS : False
  OWNDATA : True
  WRITEABLE : True
  ALIGNED : True
  UPDATEIFCOPY : False

In numpy 1.6

>>> a = np.ones((10, 10))
>>> np.copy(a.T).flags
  C_CONTIGUOUS : False
  F_CONTIGUOUS : True
  OWNDATA : True
  WRITEABLE : True
  ALIGNED : True
  UPDATEIFCOPY : False

I suggest to put "order='K'" by default in numpy 1.7 (maybe with a FutureWarning) to ensure backward compat.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0