v1.1.2.rst

What's new in 1.1.2 (September 8, 2020)

These are the changes in pandas 1.1.2. See :ref:`release` for a full changelog including other versions of pandas.

{{ header }}

Fixed regressions

• Regression in :meth:`DatetimeIndex.intersection` incorrectly raising AssertionError when intersecting against a list (:issue:`35876`)
• Fix regression in updating a column inplace (e.g. using df['col'].fillna(.., inplace=True)) (:issue:`35731`)
• Fix regression in :meth:`DataFrame.append` mixing tz-aware and tz-naive datetime columns (:issue:`35460`)
• Performance regression for :meth:`RangeIndex.format` (:issue:`35712`)
• Regression where :meth:`MultiIndex.get_loc` would return a slice spanning the full index when passed an empty list (:issue:`35878`)
• Fix regression in invalid cache after an indexing operation; this can manifest when setting which does not update the data (:issue:`35521`)
• Regression in :meth:`DataFrame.replace` where a TypeError would be raised when attempting to replace elements of type :class:`Interval` (:issue:`35931`)
• Fix regression in pickle roundtrip of the closed attribute of :class:`IntervalIndex` (:issue:`35658`)
• Fixed regression in :meth:`DataFrameGroupBy.agg` where a ValueError: buffer source array is read-only would be raised when the underlying array is read-only (:issue:`36014`)
• Fixed regression in :meth:`Series.groupby.rolling` number of levels of :class:`MultiIndex` in input was compressed to one (:issue:`36018`)
• Fixed regression in :class:`DataFrameGroupBy` on an empty :class:`DataFrame` (:issue:`36197`)

Bug fixes

• Bug in :meth:`DataFrame.eval` with object dtype column binary operations (:issue:`35794`)
• Bug in :class:`Series` constructor raising a TypeError when constructing sparse datetime64 dtypes (:issue:`35762`)
• Bug in :meth:`DataFrame.apply` with result_type="reduce" returning with incorrect index (:issue:`35683`)
• Bug in :meth:`Series.astype` and :meth:`DataFrame.astype` not respecting the errors argument when set to "ignore" for extension dtypes (:issue:`35471`)
• Bug in :meth:`DateTimeIndex.format` and :meth:`PeriodIndex.format` with name=True setting the first item to "None" where it should be "" (:issue:`35712`)
• Bug in :meth:`Float64Index.__contains__` incorrectly raising TypeError instead of returning False (:issue:`35788`)
• Bug in :class:`Series` constructor incorrectly raising a TypeError when passed an ordered set (:issue:`36044`)
• Bug in :meth:`Series.dt.isocalendar` and :meth:`DatetimeIndex.isocalendar` that returned incorrect year for certain dates (:issue:`36032`)
• Bug in :class:`DataFrame` indexing returning an incorrect :class:`Series` in some cases when the series has been altered and a cache not invalidated (:issue:`33675`)
• Bug in :meth:`DataFrame.corr` causing subsequent indexing lookups to be incorrect (:issue:`35882`)
• Bug in :meth:`import_optional_dependency` returning incorrect package names in cases where package name is different from import name (:issue:`35948`)
• Bug when setting empty :class:`DataFrame` column to a :class:`Series` in preserving name of index in frame (:issue:`31368`)

Other

• :meth:`factorize` now supports na_sentinel=None to include NaN in the uniques of the values and remove dropna keyword which was unintentionally exposed to public facing API in 1.1 version from :meth:`factorize` (:issue:`35667`)
• :meth:`DataFrame.plot` and :meth:`Series.plot` raise UserWarning about usage of FixedFormatter and FixedLocator (:issue:`35684` and :issue:`35945`)

Contributors

.. contributors:: v1.1.1..v1.1.2