RetroSearch Browse

Wed Apr 15 18:42:19 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-April/139156.html

On Wed, Apr 15, 2015 at 11:43 AM, Lennart Regebro <regebro at gmail.com> wrote:
> On Wed, Apr 15, 2015 at 11:10 AM, Chris Angelico <rosuav at gmail.com> wrote:
>> Bikeshed: Would arithmetic be based on UTC time or Unix time? It'd be
>> more logical to describe it as "adding six hours means adding six
>> hours to the UTC time", but it'd look extremely odd when there's a
>> leap second.
>
> It would ignore leap seconds. If you want to call that unix time or
> not is a matter of opinion. Hm. I guess the internal representation
> *could* be EPOCH + offset, and local times could be calculated
> properties, which could be cached (or possibly calculated at
> creation).

In any case there wold probably need to be a PEP on that, and that
means PEP 431 wouldn't make it into 3.5, unless somebody smarter than
me want to take a shot at it.

//Lennart

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-April/139156.html below:

[Python-Dev] Status on PEP-431 Timezones