R. David Murray rdmur...@bitdance.com 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
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
assignee: georg.brandl - d...@python
nosy: +d...@python
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7699
___
New submission from Michael Stephens m...@mikej.st:
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
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
priority: - normal
stage: - patch review
versions: +Python 2.6, Python 3.1, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7699
Michael Stephens m...@mikej.st 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'.
