[issue7699] strptime, strftime documentation

R. David Murray added the comment: This was applied by Georg in SVN revision r77561 on 2010-01-17. -- nosy: +r.david.murray resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker

[issue7699] strptime, strftime documentation

Changes by Mark Lawrence : -- assignee: georg.brandl -> d...@python nosy: +d...@python ___ Python tracker ___ ___ Python-bugs-list mail

[issue7699] strptime, strftime documentation

Michael Stephens added the comment: I think it's referring to: >>> datetime.time(10, 34, 6).strftime("%Y-%m-%d %H:%M:%S") '1900-01-01 10:34:06' and thus still applies. It is wrong about month and day being replaced by '0', however, and I've updated the patch to change that to '1'. --

[issue7699] strptime, strftime documentation

Brian Curtin added the comment: Seems reasonable. Additionally, the block about time.strftime not utilizing date related formats (line 1514 in the patched file) can be removed. It has worked for a long time (forever?). >>> time.strftime("%Y-%m-%d %H:%M:%S", time.localtime()) '2010-01-13 21:

[issue7699] strptime, strftime documentation

Changes by Ezio Melotti : -- nosy: +ezio.melotti priority: -> normal stage: -> patch review versions: +Python 2.6, Python 3.1, Python 3.2 ___ Python tracker ___

[issue7699] strptime, strftime documentation

New submission from Michael Stephens : The documentation for strftime and strptime behavior strikes me as a bit jumbled right now. The behavior of datetime.datetime.strptime is explained by a reference to time.strptime, which in turn references time.strftime to explain the format string. The