Issue 32267: strptime misparses offsets with microsecond format (original) (raw)

Issue32267

Created on 2017-12-10 10:12 by mariocj89, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 4781 merged mariocj89,2017-12-10 10:14
Messages (1)
msg307952 - (view) Author: Mario Corchero (mariocj89) * (Python triager) Date: 2017-12-10 10:11
At the moment strptime misparses all microsecond specifications that do not have exactly 6 digits as it is just converted into an int and considered microsecond. This bug was introduced with the implementation in bpo-31800 Example: _strptime._strptime("+01:30:30.001", "%z") == _strptime._strptime("+01:30:30.000001", "%z")
History
Date User Action Args
2022-04-11 14:58:55 admin set github: 76448
2018-01-09 21:39:26 belopolsky set status: open -> closedresolution: fixedstage: patch review -> resolved
2017-12-13 02:08:18 belopolsky set nosy: + p-ganssle
2017-12-10 21:30:04 r.david.murray set nosy: + belopolsky
2017-12-10 10:14:17 mariocj89 set keywords: + patchstage: patch reviewpull_requests: + <pull%5Frequest4682>
2017-12-10 10:12:00 mariocj89 create