You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BUG: Handle floating point boundaries in qcut (#59409)
* Handle floating point boundaries
* Mypy errors don't go away just because I didn't check them
---------
Co-authored-by: Matthew Roeschke <[email protected]>
Copy file name to clipboardExpand all lines: doc/source/whatsnew/v3.0.0.rst
+1
Original file line number
Diff line number
Diff line change
@@ -618,6 +618,7 @@ Groupby/resample/rolling
618
618
619
619
Reshaping
620
620
^^^^^^^^^
621
+
- Bug in :func:`qcut` where values at the quantile boundaries could be incorrectly assigned (:issue:`59355`)
621
622
- Bug in :meth:`DataFrame.join` inconsistently setting result index name (:issue:`55815`)
622
623
- Bug in :meth:`DataFrame.unstack` producing incorrect results when ``sort=False`` (:issue:`54987`, :issue:`55516`)
623
624
- Bug in :meth:`DataFrame.unstack` producing incorrect results when manipulating empty :class:`DataFrame` with an :class:`ExtentionDtype` (:issue:`59123`)
0 commit comments