diff options
| author | Matti Picus <matti.picus@gmail.com> | 2020-07-25 20:46:12 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-07-25 20:46:12 +0300 |
| commit | f457a1a9e9b5e5fff92dd5735052e7654b167de7 (patch) | |
| tree | 680670808d8cffd8c7d86e84739204eeadc6e8d6 /doc/release | |
| parent | 6c8be6a7bdfc1a262199658ed4d17d7f3c39711a (diff) | |
| parent | fe708577504f590d1c51f8505296686ea0106efa (diff) | |
| download | numpy-f457a1a9e9b5e5fff92dd5735052e7654b167de7.tar.gz | |
Merge pull request #16815 from cjblocker/mgrid-float
BUG: fix mgrid output for lower precision float inputs
Diffstat (limited to 'doc/release')
| -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. |