[issue32497] datetime.strptime creates tz naive object from value containing a tzname

Paul Ganssle added the comment: Sorry, forgot to include the link to the dateutil implementation of the fold-resolution code: https://github.com/dateutil/dateutil/pull/517/files -- ___ Python tracker

[issue32497] datetime.strptime creates tz naive object from value containing a tzname

Paul Ganssle added the comment: By the way, one possibly significant problem with this interface is that it would tend to encourage the use of static timezone offsets rather than rule sets as intended by `tzinfo`. The main problem is that a simple mapping between tzname

[issue32497] datetime.strptime creates tz naive object from value containing a tzname

Paul Ganssle added the comment: This is essentially what the `tzinfos` argument to `dateutil.parser.parse` does. I do think something *like* this is the only reasonable way to handle %Z->tzinfo mappings. In `dateutil`

[issue32497] datetime.strptime creates tz naive object from value containing a tzname

Change by Arjan Keeman : -- keywords: +patch pull_requests: +4973 stage: -> patch review ___ Python tracker ___

[issue32497] datetime.strptime creates tz naive object from value containing a tzname

New submission from Arjan Keeman : Consider the following: tz_naive_object = datetime.strptime("2018-01-05 13:10:00 CET", "%Y-%m-%d %H:%M:%S %Z") Python's standard library is not capable of converting the timezone name CET to a tzinfo object. Therefore the case made