Skip to content

Commit 88cb3de

Browse files
committed
DOC: add whatsnew entry for date_range DST normalize bug (GH#62602)
1 parent 0ec95f8 commit 88cb3de

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

doc/source/whatsnew/v3.0.0.rst

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -983,6 +983,7 @@ Timedelta
983983

984984
Timezones
985985
^^^^^^^^^
986+
- Bug in :func:`pandas.date_range` where using ``normalize=True`` could raise ``NonExistentTimeError`` or ``AmbiguousTimeError`` when crossing DST transitions, even if ``nonexistent`` or ``ambiguous`` parameters were specified. (:issue:`62602`)
986987
- Bug in :meth:`DatetimeIndex.union`, :meth:`DatetimeIndex.intersection`, and :meth:`DatetimeIndex.symmetric_difference` changing timezone to UTC when merging two DatetimeIndex objects with the same timezone but different units (:issue:`60080`)
987988
- Bug in :meth:`Series.dt.tz_localize` with a timezone-aware :class:`ArrowDtype` incorrectly converting to UTC when ``tz=None`` (:issue:`61780`)
988989
- Fixed bug in :func:`date_range` where tz-aware endpoints with calendar offsets (e.g. ``"MS"``) failed on DST fall-back. These now respect ``ambiguous``/ ``nonexistent``. (:issue:`52908`)

0 commit comments

Comments
 (0)