diff options
| author | Sebastian Berg <sebastianb@nvidia.com> | 2023-05-04 17:54:17 +0200 |
|---|---|---|
| committer | Sebastian Berg <sebastianb@nvidia.com> | 2023-05-04 17:54:17 +0200 |
| commit | 6c394e3d485f3a522d6e7242a577ee04a9126e0b (patch) | |
| tree | abb295d75203094da99f2392575f5b7b119b32f0 /doc | |
| parent | ec8d5db302c0e8597feb058f58863d5e9a6554c1 (diff) | |
| download | numpy-6c394e3d485f3a522d6e7242a577ee04a9126e0b.tar.gz | |
DOC: Add release note for uint64/int64 comparison change
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/release/upcoming_changes/23713.improvement.rst | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/release/upcoming_changes/23713.improvement.rst b/doc/release/upcoming_changes/23713.improvement.rst new file mode 100644 index 000000000..15a4f412b --- /dev/null +++ b/doc/release/upcoming_changes/23713.improvement.rst @@ -0,0 +1,9 @@ +Signed and unsigned integers always compare correctly +----------------------------------------------------- +When ``uint64`` and ``int64`` are mixed in NumPy, NumPy typically +promotes both to ``float64``. This behavior may be argued about +but is confusing for comparisons ``==``, ``<=``, since the results +returned can be incorrect but the conversion is hidden since the +result is a boolean. +NumPy will now return the correct results for these by avoiding +the cast to float. |