summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJay Bourque <jay.bourque@continuum.io>2012-07-17 13:43:18 -0500
committerJay Bourque <jay.bourque@continuum.io>2012-07-17 16:05:10 -0500
commitbf58296eae309e92d8632bad4f52d602cb8c0f22 (patch)
tree61acc48127794008493576722acc78779536acd3 /doc
parent781468b5938ce1a79804613b222063d81e99963d (diff)
downloadnumpy-bf58296eae309e92d8632bad4f52d602cb8c0f22.tar.gz
update 1.7 release notes
Diffstat (limited to 'doc')
-rw-r--r--doc/release/1.7.0-notes.rst7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/release/1.7.0-notes.rst b/doc/release/1.7.0-notes.rst
index e8b1de72d..824b8f14b 100644
--- a/doc/release/1.7.0-notes.rst
+++ b/doc/release/1.7.0-notes.rst
@@ -26,6 +26,13 @@ functions. To facilitate this transition, numpy 1.7 produces a
FutureWarning if it detects that you may be attempting to write to
such an array. See the documentation for np.diagonal for details.
+Similar to np.diagonal above, in a future version of numpy, indexing
+a record array by a list of field names will return a view onto the
+original array, instead of producing a copy as they do now. As with
+np.diagonal, numpy 1.7 produces a DeprecationWarning if it detects
+that you may be attemping to write to such an array. See the documentation
+for array indexing for details.
+
The default casting rule for UFunc out= parameters has been changed from
'unsafe' to 'same_kind'. Most usages which violate the 'same_kind'
rule are likely bugs, so this change may expose previously undetected