summaryrefslogtreecommitdiff
path: root/numpy/core/numeric.py
diff options
context:
space:
mode:
authorSebastian Berg <sebastian@sipsolutions.net>2012-10-21 18:34:04 +0200
committerSebastian Berg <sebastian@sipsolutions.net>2012-10-21 18:37:38 +0200
commit4b281479db093a55c010610ad287c75beb6da13b (patch)
tree5dbf562060839089603db307e3d96ed4da240abf /numpy/core/numeric.py
parentfb64bbf12f2405b3dc97f7736ae3dc35daf615dc (diff)
downloadnumpy-4b281479db093a55c010610ad287c75beb6da13b.tar.gz
API: Change isfortran to f-contig and not c-contig
This was a check for 1-d arrays, this is the generalization to higher dimension if we allow higher dimensioal arrays to be both f- and c-contiguous.
Diffstat (limited to 'numpy/core/numeric.py')
-rw-r--r--numpy/core/numeric.py4
1 files changed, 2 insertions, 2 deletions
diff --git a/numpy/core/numeric.py b/numpy/core/numeric.py
index 5f0474d3e..0d0babbac 100644
--- a/numpy/core/numeric.py
+++ b/numpy/core/numeric.py
@@ -538,7 +538,7 @@ def require(a, dtype=None, requirements=None):
def isfortran(a):
"""
Returns True if array is arranged in Fortran-order in memory
- and dimension > 1.
+ and not C-order.
Parameters
----------
@@ -584,7 +584,7 @@ def isfortran(a):
>>> np.isfortran(b)
True
- 1-D arrays always evaluate as False.
+ C-ordered arrays evaluate as False even if they are also FORTRAN-ordered.
>>> np.isfortran(np.array([1, 2], order='FORTRAN'))
False