[issue25963] strptime not parsing some timezones

Andrei Kulakov added the comment: I'm closing this as fixed, the note in datetime docs is here: https://docs.python.org/3.9/library/datetime.html (search for 'only accepts', - note 6) -- nosy: +kj resolution: -> fixed stage: -> resolved status: open -> closed versions: +Python 3.9

[issue25963] strptime not parsing some timezones

Andrei Kulakov added the comment: This was fixed so can be closed. Current datetime docs have a footnote for %Z: ... strptime() only accepts certain values for %Z: any value in time.tzname for your machine’s locale the hard-coded values UTC and GMT -- nosy: +andrei.avk

[issue25963] strptime not parsing some timezones

Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue25963] strptime not parsing some timezones

R. David Murray added the comment: The code is shared by the two modules (it's in _strptime.py). So, yes. There is clearly a doc bug here (%Z needs a footnote in the table in the datetime docs), but there is no practical way to implement the parsing of arbitrary (non-locale) timezone strings,

[issue25963] strptime not parsing some timezones

Martin Panter added the comment: I suspect the datetime module’s %Z parsing depends on the locale, just like time.strptime() does: . -- nosy: +martin.panter ___ Python tracker

[issue25963] strptime not parsing some timezones

New submission from Utkonos: I get a ValueError when running the following through strptime: datetime.datetime.strptime('(CST)', '(%Z)') But the following works: datetime.datetime.strptime('(EST)', '(%Z)') PST and MST also trigger the same exception. -- messages: 257108 nosy: belopols