summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNathaniel J. Smith <njs@pobox.com>2012-07-17 16:56:04 +0100
committerNathaniel J. Smith <njs@pobox.com>2012-07-17 17:00:38 +0100
commitb798f12abac2c5ac807fe9f523fd89e57efaa57c (patch)
tree73d3a9a0a2e21a86d495ebbab60a0729fdaa98df /doc
parent1234d1ccc891c427e090eff6d45f8e195330f96a (diff)
downloadnumpy-b798f12abac2c5ac807fe9f523fd89e57efaa57c.tar.gz
Switch WARN_ON_WRITE to issuing FutureWarnings instead of DeprecationWarnings
FutureWarnings are displayed by default, so they should be used whenever a future change will change the semantics of existing code (as opposed to making existing code simply stop working). List discussion: http://www.mail-archive.com/numpy-discussion@scipy.org/msg37500.html
Diffstat (limited to 'doc')
-rw-r--r--doc/release/1.7.0-notes.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/release/1.7.0-notes.rst b/doc/release/1.7.0-notes.rst
index e5c8b300a..e8b1de72d 100644
--- a/doc/release/1.7.0-notes.rst
+++ b/doc/release/1.7.0-notes.rst
@@ -23,8 +23,8 @@ the diagonal method of ndarrays will return a view onto the original
array, instead of producing a copy as they do now. This makes a
difference if you write to the array returned by any of these
functions. To facilitate this transition, numpy 1.7 produces a
-DeprecationWarning if it detects that you may be attempting to write
-to such an array. See the documentation for np.diagonal for details.
+FutureWarning if it detects that you may be attempting to write to
+such an array. See the documentation for np.diagonal 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'