Paul Ganssle <[email protected]> added the comment:
This is a duplicate of issue 13305.
Right now we have some shims around `strftime` to improve consistency in some
situations and for other reasons, but mostly we just call the libc version.
There is an open issue from 2008 (#3173) to ship our own implementation of
strftime that could smooth out some of these issues and try and make the
behavior more consistent (though presumably some people have started to rely on
platform-specific behaviors by now, so it may be a decent amount of work to
roll it out).
I'm going to close this in favor of 13305, but thanks for reporting it!
----------
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> datetime.strftime("%Y") not consistent for years < 1000
type: -> behavior
_______________________________________
Python tracker <[email protected]>
<https://bugs.python.org/issue39103>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
