These are the changes in pandas 1.0.4. See :ref:`release` for a full changelog including other versions of pandas.
{{ header }}
- Bug where :meth:`Series.isna` and :meth:`DataFrame.isna` would raise for categorical dtype when
pandas.options.mode.use_inf_as_na
was set toTrue
(:issue:`33594`) - Bug in :meth:`GroupBy.first` and :meth:`GroupBy.last` where None is not preserved in object dtype (:issue:`32800`)
- Bug in DataFrame reductions using
numeric_only=True
and ExtensionArrays (:issue:`33256`). - Fix performance regression in
memory_usage(deep=True)
for object dtype (:issue:`33012`) - Bug where :meth:`Categorical.replace` would replace with
NaN
whenever the new value and replacement value were equal (:issue:`33288`) - Bug where an ordered :class:`Categorical` containing only
NaN
values would raise rather than returningNaN
when taking the minimum or maximum (:issue:`33450`) - Bug in :meth:`DataFrameGroupBy.agg` with dictionary input losing
ExtensionArray
dtypes (:issue:`32194`) - Fix to preserve the ability to index with the "nearest" method with xarray's CFTimeIndex, an :class:`Index` subclass (pydata/xarray#3751, :issue:`32905`).
- Fix regression in :meth:`DataFrame.describe` raising
TypeError: unhashable type: 'dict'
(:issue:`32409`)
- Bug in :meth:`SeriesGroupBy.first`, :meth:`SeriesGroupBy.last`, :meth:`SeriesGroupBy.min`, and :meth:`SeriesGroupBy.max` returning floats when applied to nullable Booleans (:issue:`33071`)
- Bug in :meth:`Rolling.min` and :meth:`Rolling.max`: Growing memory usage after multiple calls when using a fixed window (:issue:`30726`)
.. contributors:: v1.0.3..v1.0.4|HEAD