diff options
author | Jay Bourque <jay.bourque@continuum.io> | 2012-07-17 16:03:41 -0500 |
---|---|---|
committer | Jay Bourque <jay.bourque@continuum.io> | 2012-07-17 16:05:10 -0500 |
commit | a03e8b4d286e91ef5823c059dcfb7a52ce420725 (patch) | |
tree | cf85c4c76a7591b874726bf6ed0d391dcf152c46 /doc/source | |
parent | 2eb9610acab872538742ce7db5cbbae6cb23360e (diff) | |
download | numpy-a03e8b4d286e91ef5823c059dcfb7a52ce420725.tar.gz |
change DeprecationWarning to FutureWarning
Diffstat (limited to 'doc/source')
-rw-r--r-- | doc/source/reference/arrays.indexing.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/source/reference/arrays.indexing.rst b/doc/source/reference/arrays.indexing.rst index bc12c5d0e..f8966f5c1 100644 --- a/doc/source/reference/arrays.indexing.rst +++ b/doc/source/reference/arrays.indexing.rst @@ -339,7 +339,7 @@ Indexing into a record array can also be done with a list of field names, *e.g.* ``x[['field-name1','field-name2']]``. Currently this returns a new array containing a copy of the values in the fields specified in the list. As of NumPy 1.7, returning a copy is being deprecated in favor of returning -a view. A copy will continue to be returned for now, but a DeprecationWarning +a view. A copy will continue to be returned for now, but a FutureWarning will be issued when writing to the copy. If you depend on the current behavior, then we suggest copying the returned array explicitly, i.e. use x[['field-name1','field-name2']].copy(). This will work with both past and |