random...@fastmail.us writes:
I would argue that it _should_ be, and that it should populate it with 0
in gmtime or either with timezone/altzone or by some sort of reverse
calculation in localtime, but it is not. Another problem to add to my
list of reasons for my recent python-ideas
On Mon, Sep 16, 2013, at 16:55, Michael Schwarz wrote:
On 2013-W38-1, at 19:56, random...@fastmail.us wrote:
On Mon, Sep 16, 2013, at 9:15, Michael Schwarz wrote:
According to the documentation of time.gmtime(), it returns a struct_time
in UTC, but %z is replaced by +0100, which is the
I’m wondering whether this is expected:
Python 3.3.2 (default, May 21 2013, 11:50:47)
[GCC 4.2.1 Compatible Apple Clang 4.1 ((tags/Apple/clang-421.11.66))] on darwin
Type help, copyright, credits or license for more information.
import time
time.strftime(%F %T %z, time.gmtime(40 * 365 *
On Mon, Sep 16, 2013, at 9:15, Michael Schwarz wrote:
According to the documentation of time.gmtime(), it returns a struct_time
in UTC, but %z is replaced by +0100, which is the UTC offset of my OS’s
time zone without DST, but DST is currently in effect here (but was not
at the timestamp
On 2013-W38-1, at 19:56, random...@fastmail.us wrote:
On Mon, Sep 16, 2013, at 9:15, Michael Schwarz wrote:
According to the documentation of time.gmtime(), it returns a struct_time
in UTC, but %z is replaced by +0100, which is the UTC offset of my OS’s
time zone without DST, but DST is
