On 09/06/2014 03:19 PM, Guido van Rossum wrote:
On Sat, Sep 6, 2014 at 2:56 PM, random832 wrote:
But, as I've advocated before, there's no fundamental reason that python should chain itself to the C library's underlying implementation rather than defining its own time functions that do always use an epoch of 1970, and handle leap seconds consistently, have unlimited range, etc.
I'm fine with that, as long as "handle leap seconds consistently" means "pretend they don't exist" (which is necessary for compatibility with POSIX). But it sounds like a big coding project. Fixing the docs to be consistent and correctly describe the current implementation may be simpler.
Or at least fix the docs until the new project is done, and then we can fix them again. :)