Alexander Belopolsky <alexander.belopol...@gmail.com> added the comment:
On Sun, Jan 2, 2011 at 6:29 PM, Georg Brandl <rep...@bugs.python.org> wrote: .. > You cannot have both: a safe implementation and the correct behavior with > glibc > (not Linux!) -- except if you start special-casing. Not sure that's worth it. > That's the reason why this and the related ctime issue were lingering for so long. My plan was to pick the low-hanging fruit (the null check) for 3.3 and leave proper bounds checking and possibly switch to reentrant APIs for the next release. 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. Given that datetime module does not have these issues, I don't see this as "must fix." ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8013> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
