These are the changes in pandas 1.5.3. See release
for a full changelog including other versions of pandas.
{{ header }}
- Fixed performance regression in
Series.isin
whenvalues
is empty (49839
) - Fixed regression in
DataFrame.memory_usage
showing unnecessaryFutureWarning
whenDataFrame
is empty (50066
) - Fixed regression in
.DataFrameGroupBy.transform
when used withas_index=False
(49834
) - Enforced reversion of
color
as an alias forc
andsize
as an alias fors
in functionDataFrame.plot.scatter
(49732
) - Fixed regression in
.SeriesGroupBy.apply
setting aname
attribute on the result if the result was aDataFrame
(49907
) - Fixed performance regression in setting with the
~DataFrame.at
indexer (49771
) - Fixed regression in the methods
apply
,agg
, andtransform
when used with NumPy functions that informed users to supplynumeric_only=True
if the operation failed on non-numeric dtypes; such columns must be dropped prior to using these methods (50538
)
- Bug in the Copy-on-Write implementation losing track of views when indexing a
DataFrame
with anotherDataFrame
(50630
) - Bug in
.Styler.to_excel
leading to error when unrecognizedborder-style
(e.g."hair"
) provided to Excel writers (48649
) - Bug in
Series.quantile
emitting warning from NumPy whenSeries
has onlyNA
values (50681
) - Bug when chaining several
.Styler.concat
calls, only the last styler was concatenated (49207
) - Fixed bug when instantiating a
DataFrame
subclass inheriting fromtyping.Generic
that triggered aUserWarning
on python 3.11 (49649
) - Bug in
pivot_table
with NumPy 1.24 or greater when theDataFrame
columns has nested elements (50342
) - Bug in
pandas.testing.assert_series_equal
(and equivalentassert_
functions) when having nested data and using numpy >= 1.25 (50360
)
Note
If you are using DataFrame.to_sql
, read_sql
, read_sql_table
, or read_sql_query
with SQLAlchemy 1.4.46 or greater, you may see a sqlalchemy.exc.RemovedIn20Warning
. These warnings can be safely ignored for the SQLAlchemy 1.4.x releases as pandas works toward compatibility with SQLAlchemy 2.0.
- Reverted deprecation (
45324
) of behavior ofSeries.__getitem__
andSeries.__setitem__
slicing with an integerIndex
; this will remain positional (49612
) - A
FutureWarning
raised when attempting to set values inplace withDataFrame.loc
orDataFrame.loc
has been changed to aDeprecationWarning
(48673
)
v1.5.2..v1.5.3|HEAD