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: DateTimeIndex.is_year_start unexpected behavior when constructed with freq 'MS' date_range (#57377) (#57494)
* Added some comments to where the bug is occurring
* Potential fix, passed all potentially relevant tests
* Very likely fix
* Reverted ro previous start/end scheme; added tests
* Added fixes to whatsnew doc
* Removed stray comment
* Fixed alphabetical problem in whatsnew
* add parametric test
* fixup
---------
Co-authored-by: Marco Gorelli <[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
@@ -481,6 +481,7 @@ Categorical
481
481
482
482
Datetimelike
483
483
^^^^^^^^^^^^
484
+
- Bug in :attr:`is_year_start` where a DateTimeIndex constructed via a date_range with frequency 'MS' wouldn't have the correct year or quarter start attributes (:issue:`57377`)
484
485
- Bug in :class:`Timestamp` constructor failing to raise when ``tz=None`` is explicitly specified in conjunction with timezone-aware ``tzinfo`` or data (:issue:`48688`)
485
486
- Bug in :func:`date_range` where the last valid timestamp would sometimes not be produced (:issue:`56134`)
486
487
- Bug in :func:`date_range` where using a negative frequency value would not include all points between the start and end values (:issue:`56382`)
0 commit comments