Skip to content

[3.7] bpo-37642: Update max and min offset in datetime module (GH-14878) #15226

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

Merged
merged 1 commit into from
Aug 15, 2019

Conversation

pganssle
Copy link
Member

@pganssle pganssle commented Aug 12, 2019

This fixes an inconsistency between the Python and C implementations of
the datetime module. The pure python version of the code was not
accepting offsets greater than 23:59 but less than 24:00. This is an
accidental legacy of the original implementation, which was put in place
before tzinfo allowed sub-minute time zone offsets.

GH-14878

(cherry picked from commit 92c7e30)

https://bugs.python.org/issue37642

This fixes an inconsistency between the Python and C implementations of
the datetime module. The pure python version of the code was not
accepting offsets greater than 23:59 but less than 24:00. This is an
accidental legacy of the original implementation, which was put in place
before tzinfo allowed sub-minute time zone offsets.

pythonGH-14878

(cherry picked from commit 92c7e30)
@pganssle pganssle force-pushed the backport-92c7e30-3.7 branch from 8628fca to 6154aed Compare August 12, 2019 14:26
@pganssle
Copy link
Member Author

CC @nsiregar

@pganssle pganssle merged commit ed44b84 into python:3.7 Aug 15, 2019
@pganssle pganssle deleted the backport-92c7e30-3.7 branch August 15, 2019 19:09
@bedevere-bot
Copy link

@pganssle: Please replace # with GH- in the commit message next time. Thanks!

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.

4 participants