gh-126883: Add check that timezone fields are in range for datetime.fromisoformat - #127242
Conversation
|
I haven't had a chance for a through review yet, but I'm in favor of the general approach and a casual glance looks good. Can you add a news blurb (credit yourself appropriately unless you don't want that for some reason), and if you aren't already in ACKS please add yourself there (again unless you don't want to be acknowledged for some reason). |
|
@erlend-aasland maybe you have free time to review and merge it |
erlend-aasland
left a comment
There was a problem hiding this comment.
Can you please remove any unneeded style changes?
Co-authored-by: Erlend E. Aasland <erlend.aasland@protonmail.com>
|
cc @pganssle @erlend-aasland |
pganssle
left a comment
There was a problem hiding this comment.
Some minor nits, but overall looks good!
Co-authored-by: Paul Ganssle <1377457+pganssle@users.noreply.github.com>
|
Thanks @donbarbos, great work on this and sorry for the long delay. |
…etime.fromisoformat` (python#127242) It was previously possible to specify things like `+00:90:00` which would be equivalent to `+01:30:00`, but is not a valid ISO8601 string. --------- Co-authored-by: Erlend E. Aasland <erlend.aasland@protonmail.com> Co-authored-by: Paul Ganssle <1377457+pganssle@users.noreply.github.com>
…etime.fromisoformat` (python#127242) It was previously possible to specify things like `+00:90:00` which would be equivalent to `+01:30:00`, but is not a valid ISO8601 string. --------- Co-authored-by: Erlend E. Aasland <erlend.aasland@protonmail.com> Co-authored-by: Paul Ganssle <1377457+pganssle@users.noreply.github.com>

CimplementationPythonimplementationAlso error output for the
time.fromisoformatfunction was fixed as indatetime.fromisoformatin Python implementationdatetime.fromisoformat()parses offset minutes outside 00-59 range #126883