summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--numpy/add_newdocs.py6
-rw-r--r--numpy/ma/core.py6
2 files changed, 12 insertions, 0 deletions
diff --git a/numpy/add_newdocs.py b/numpy/add_newdocs.py
index 26711f177..d1f6b3285 100644
--- a/numpy/add_newdocs.py
+++ b/numpy/add_newdocs.py
@@ -4460,6 +4460,12 @@ add_newdoc('numpy.core.multiarray', 'ndarray', ('view',
(same shape, dtype, etc.) This does not cause a reinterpretation of the
memory.
+ In cases when ``a.view(some_dtype)`` causes a reinterpretation of the
+ bytes of memory, its behavior cannot necessarily be predicted just from
+ the superficial appearance of ``a`` (shown by ``print(a)``). If ``a`` is
+ C-ordered versus fortran-ordered, versus defined as a transpose, versus
+ defined as a slice, etc., the view may give different results.
+
Examples
--------
diff --git a/numpy/ma/core.py b/numpy/ma/core.py
index dbd619b80..e895f8269 100644
--- a/numpy/ma/core.py
+++ b/numpy/ma/core.py
@@ -2889,6 +2889,12 @@ class MaskedArray(ndarray):
`dtype` is an ndarray sub-class), then the fill value is preserved.
Finally, if `fill_value` is specified, but `dtype` is not, the fill
value is set to the specified value.
+
+ In cases when ``a.view(some_dtype)`` causes a reinterpretation of the
+ bytes of memory, its behavior cannot necessarily be predicted just from
+ the superficial appearance of ``a`` (shown by ``print(a)``). If ``a`` is
+ C-ordered versus fortran-ordered, versus defined as a transpose, versus
+ defined as a slice, etc., the view may give different results.
"""
if dtype is None: