TST: tz_localize nonexistent shift across UTC+0 DST boundary (GH#40705)#66019
Merged
Conversation
Add Europe/London cases to test_dti_tz_localize_nonexistent_shift covering the UTC+0 -> UTC+1 transition, including the timedelta nonexistent shift from GH#40705 and the shift_forward form from GH#40915. Both were fixed by GH#56017 but lacked DatetimeIndex coverage at the UTC+0 boundary. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
jbrockmendel
added
Testing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes #40705
closes #40915
Add Europe/London cases to
test_dti_tz_localize_nonexistent_shiftcovering the UTC+0 → UTC+1 DST transition. Thetimedeltanonexistent shift is the exact reproducer from GH-40705 (previously off by an hour), and theshift_forwardform covers GH-40915. Both were fixed by GH-56017, but that PR only added scalarTimestampcoverage at the UTC+0 boundary — theDatetimeIndexpath and thetimedeltavariant were untested.