[issue8013] time.asctime segfaults when given a time in the far future
Georg Brandl
report at bugs.python.org
Mon Jan 3 00:46:37 CET 2011
Georg Brandl <georg at python.org> added the comment:
> There is a long tradition in keeping OS functions'
> wrappers thin with an expectation that application programmers will
> know the limitations/quirks of their target OSes.
Sorry, but that does not apply if we trigger undefined behavior which
is inherently unsafe, as you rightly insist.
I don't see the range checking as particularly challenging; I'm sure you can get it done in time for 3.2.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue8013>
_______________________________________
More information about the Python-bugs-list
mailing list