Tim Golden <[email protected]> added the comment:
This is happening on Windows x86 against the current tip. The MS C runtime can
handle older dates; it's just that we're taking 1900 off the year at some
point. (At least, I think that's what's happening). FWIW you only need
time.strftime to reproduce the error:
import time
time.strftime("%y", (1899, 1, 1, 0, 0, 0, 0, 0, 0))
If no-one gets there first I'll dig into the timemodule strftime wrapper.
----------
nosy: +tim.golden
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue13674>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
