[issue10827] Functions in time module should support year < 1900 when accept2dyear = 0

Alexander Belopolsky report at bugs.python.org
Tue Jan 4 19:38:57 CET 2011


Alexander Belopolsky <belopolsky at users.sourceforge.net> added the comment:

On Tue, Jan 4, 2011 at 1:30 PM, Alexander Belopolsky
<report at bugs.python.org> wrote:
..
> This is clearly a bug.  (Although Y2K note contradicts time.accept2dyear documentation.)
>

PyObject_IsTrue() may fail - this is probably the reason for the
current odd logic.  My patch should be fixed top respect that, but I
still maintain that time.accept2dyear = True should work as expected.
(Would also make True the default rather 1.)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10827>
_______________________________________


More information about the Python-bugs-list mailing list