diff options
| author | Charles Harris <charlesr.harris@gmail.com> | 2016-01-01 19:00:27 -0700 |
|---|---|---|
| committer | Charles Harris <charlesr.harris@gmail.com> | 2016-01-02 20:05:14 -0700 |
| commit | bc2a97bde26a026e75adec7ec70566be3005c47c (patch) | |
| tree | 55aa684e2a30b4859bb6fe24b2b18b51a7cb169e | |
| parent | 07fa8cc957880614319aeb5b88c88ae367d954d9 (diff) | |
| download | numpy-bc2a97bde26a026e75adec7ec70566be3005c47c.tar.gz | |
DOC: Document new randint dtype parameter in 1.11.0 release notes.
| -rw-r--r-- | doc/release/1.11.0-notes.rst | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/release/1.11.0-notes.rst b/doc/release/1.11.0-notes.rst index 7c078eed9..705ce73c1 100644 --- a/doc/release/1.11.0-notes.rst +++ b/doc/release/1.11.0-notes.rst @@ -86,6 +86,23 @@ New Features the files can be specifies to be ``*.f90``. The ``verbose`` argument is also activated, it was previously ignored. +* A ``dtype`` parameter has been added to ``np.random.randint`` + Random ndarrays of the following types can now be generated: + + - np.bool, + - np.int8, np.uint8, + - np.int16, np.uint16, + - np.int32, np.uint32, + - np.int64, np.uint64, + - np.int_ (long), np.intp + + The specification is by precision rather than by C type. Hence, on some + platforms np.int64 may be a `long` instead of `long long` even if the + specified dtype is `long long` because the two may have the same + precision. The resulting type depends on which c type numpy uses for the + given precision. The byteorder specification is also ignored, the + generated arrays are always in native byte order. + Improvements ============ |