diff options
author | Sebastian Berg <sebastian@sipsolutions.net> | 2013-12-18 13:34:55 +0100 |
---|---|---|
committer | Sebastian Berg <sebastian@sipsolutions.net> | 2014-02-06 17:52:00 +0100 |
commit | 97e9053ef7da4d6f8b4fef175604b1fdb0e5e28a (patch) | |
tree | ed080bc8c29bf065369e7f98cacb62b38bd2f895 | |
parent | d1cf9054705ab2fbd5193c9bf970b3b655076ff5 (diff) | |
download | numpy-97e9053ef7da4d6f8b4fef175604b1fdb0e5e28a.tar.gz |
DOC: Minor release notes changes
-rw-r--r-- | doc/release/1.9.0-notes.rst | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/release/1.9.0-notes.rst b/doc/release/1.9.0-notes.rst index 31ba40016..a2ee62af6 100644 --- a/doc/release/1.9.0-notes.rst +++ b/doc/release/1.9.0-notes.rst @@ -131,8 +131,7 @@ indexing operations: never reversed for compatibility reasons). This means that the result is undefined if multiple values are assigned to the same element. An example for this is ``arr[[0, 0], [1, 1]] = [1, 2]``, which may - set ``arr[0, 1]`` to either 1 or 2 depending on the memory order of the - indexing and value arrays. + set ``arr[0, 1]`` to either 1 or 2. * Equivalent to the iteration order, the memory layout of the advanced indexing result is adapted for faster indexing and cannot be predicted. * All indexing operations return a view or a copy. No indexing operation @@ -145,7 +144,7 @@ indexing operations: * All non-integer array-likes are deprecated, object arrays of custom integer like objects may have to be cast explicitly. * The error reporting for advanced indexing is more informative, however - the error type has changed in some cases. (e.g. Broadcasting errors of + the error type has changed in some cases. (Broadcasting errors of indexing arrays are reported as `IndexError`) * Indexing with more then one ellipsis (`...`) is deprecated. |