diff options
| author | Cameron Blocker <cameronjblocker@gmail.com> | 2020-07-24 17:39:23 -0400 |
|---|---|---|
| committer | Cameron Blocker <cameronjblocker@gmail.com> | 2020-07-24 17:39:23 -0400 |
| commit | fe708577504f590d1c51f8505296686ea0106efa (patch) | |
| tree | a12c9a4dff3bfbc602f26b9a7665322160668f43 | |
| parent | 7a3962dddd619ede248558da9de7d0d1a196d938 (diff) | |
| download | numpy-fe708577504f590d1c51f8505296686ea0106efa.tar.gz | |
DOC: add release note for #16815
| -rw-r--r-- | doc/release/upcoming_changes/16815.compatibility.rst | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/release/upcoming_changes/16815.compatibility.rst b/doc/release/upcoming_changes/16815.compatibility.rst new file mode 100644 index 000000000..4089b16d1 --- /dev/null +++ b/doc/release/upcoming_changes/16815.compatibility.rst @@ -0,0 +1,8 @@ +`mgrid`, `r_`, etc. fixed to consistently return correct outputs for non-default precision inputs +------------------------------------------------------------------------------------------------- +Previously, ``np.mgrid[np.float32(0.1):np.float32(0.35):np.float32(0.1),]`` +and ``np.r_[0:10:np.complex64(3j)]`` failed to return meaningful output. +This bug potentially affects `mgrid`, `ogrid`, `r_`, and `c_` when an +input with dtype other than the default `float64` and `complex128` +and equivalent Python types were used. +The methods have been fixed to handle varying precision correctly. |