Skip to content

Commit 8760066

Browse files
committed
adding whatsnew
1 parent 47fd743 commit 8760066

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

doc/source/whatsnew/v0.24.0.txt

+4-1
Original file line numberDiff line numberDiff line change
@@ -713,13 +713,16 @@ Indexing
713713
- Bug where mixed indexes wouldn't allow integers for ``.at`` (:issue:`19860`)
714714
- ``Float64Index.get_loc`` now raises ``KeyError`` when boolean key passed. (:issue:`19087`)
715715
- Bug in :meth:`DataFrame.loc` when indexing with an :class:`IntervalIndex` (:issue:`19977`)
716+
- :class:`Index` no longer mangles ``None``, ``NaN`` and ``NaT``, i.e. they are treated as three different keys. However, for numeric Index all three are still coerced to a ``NaN`` (:issue:`22332`)
716717

717718
Missing
718719
^^^^^^^
719720

720721
- Bug in :func:`DataFrame.fillna` where a ``ValueError`` would raise when one column contained a ``datetime64[ns, tz]`` dtype (:issue:`15522`)
721722
- Bug in :func:`Series.hasnans` that could be incorrectly cached and return incorrect answers if null elements are introduced after an initial call (:issue:`19700`)
722-
- :func:`Series.isin` now treats all nans as equal also for ``np.object``-dtype. This behavior is consistent with the behavior for float64 (:issue:`22119`)
723+
- :func:`Series.isin` now treats all NaN-floats as equal also for `np.object`-dtype. This behavior is consistent with the behavior for float64 (:issue:`22119`)
724+
- :func:`unique` no longer mangles NaN-floats and the ``NaT``-object for `np.object`-dtype, i.e. ``NaT`` is no longer coerced to a NaN-value and is treated as a different entity. (:issue:`22295`)
725+
723726

724727
MultiIndex
725728
^^^^^^^^^^

0 commit comments

Comments
 (0)