Skip to content
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.

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

truncate leap seconds on chrono to datetime conversions #3458

Merged
merged 1 commit into from
Sep 29, 2023

Conversation

davidhewitt
Copy link
Member

Fixes #3424

As discussed in that issue, I decided to proceed to truncate leap-seconds and emit a warning when doing so.

Most the diff is adjustment to test code to adjust for the logic, check the warning is raised and also deal with increased strictness of when leap-seconds are allowed in chrono 0.4.31.

@davidhewitt
Copy link
Member Author

I split out #3469, please review that first.

@davidhewitt davidhewitt marked this pull request as draft September 23, 2023 11:49
@davidhewitt
Copy link
Member Author

Also moved the warnings testing logic out into #3470.

@davidhewitt davidhewitt marked this pull request as ready for review September 24, 2023 19:31
@davidhewitt
Copy link
Member Author

Rebased; this now contains purely the behavioural changes plus updates to accompanying tests.

@davidhewitt
Copy link
Member Author

If I don't hear reasons not to, I'll merge this on Friday so that I can work on a fix for #3266 without having masses of conflicts.

@davidhewitt davidhewitt added this pull request to the merge queue Sep 29, 2023
Merged via the queue into PyO3:main with commit 50cb41d Sep 29, 2023
31 checks passed
@davidhewitt davidhewitt deleted the truncate-leap-seconds branch September 29, 2023 12:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Handling of leap seconds in chrono feature is probably wrong
1 participant