Skip to content

Update whatsnew for issue #53115 #61586

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 9, 2025
Merged

Update whatsnew for issue #53115 #61586

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ea3e048
update whatsnew
fbourgey Jun 6, 2025
1f7c3d4
improve message
fbourgey Jun 6, 2025
1d5239a
Merge branch 'main' into whatsnew-60898
fbourgey Jun 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions doc/source/whatsnew/v3.0.0.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -712,6 +712,7 @@ Timezones
Numeric
^^^^^^^
- Bug in :meth:`DataFrame.corr` where numerical precision errors resulted in correlations above ``1.0`` (:issue:`61120`)
- Bug in :meth:`DataFrame.cov` where presence of ``NaT`` in columns could lead to incorrect results or errors (:issue:`53115`)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's worth stating that this raises a TypeError now, rather than returning incorrect results. Also IIUC, we always raise a TypeError, regardless of the presence of NaT. So maybe

Suggested change
- Bug in :meth:`DataFrame.cov` where presence of ``NaT`` in columns could lead to incorrect results or errors (:issue:`53115`)
:meth:`DataFrame.cov` raises a ``TypeError`` instead of returning potentially incorrect results or other errors (:issue:`53115`).

- Bug in :meth:`DataFrame.quantile` where the column type was not preserved when ``numeric_only=True`` with a list-like ``q`` produced an empty result (:issue:`59035`)
- Bug in :meth:`Series.dot` returning ``object`` dtype for :class:`ArrowDtype` and nullable-dtype data (:issue:`61375`)
- Bug in ``np.matmul`` with :class:`Index` inputs raising a ``TypeError`` (:issue:`57079`)
Expand Down