New submission from Alexander Belopolsky <belopol...@users.sourceforge.net>:
""" > http://docs.python.org/library/time.html#time-y2kissues > "Values 100–1899 are always illegal." Why are these values illegal? The GNU libc accepts year in [1900-2^31; 2^31-1] (tm_year in [-2147483648; 2147481747]). If time.accept2dyear=False, we should at least accept years in [1; 9999]. The system libc would raise an error (return NULL) if it doesn't know how to format years older than 1900. """ -- Victor Stinner at msg12516 ---------- assignee: belopolsky components: Extension Modules messages: 125339 nosy: SilentGhost, belopolsky, haypo priority: normal severity: normal status: open title: Functions in time module should support year < 1900 when accept2dyear = 0 type: behavior _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10827> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
