Message51929
Looking at this a bit more, it seems like timegm (which is a pretty desirable function to have) really is as simple as the calendar.timegm function, as far as I can tell: it just throws time zone information away. So the timegm implementation in the patches so far is actually wrong (and broken in the way it attempts to use tm_gmtoff, anyway).
However, it might be nice to have a function which actually interprets times properly in order to produce a UNIX time. In other words, something which returns zero for both time.localtime(0) and time.gmtime(0), along with other times which happen to refer to the epoch but in other time zones.
I'll upload a fixed patch in the next day or so, hopefully. Sorry for the noise! |
|
Date |
User |
Action |
Args |
2007-08-23 15:56:40 | admin | link | issue1667546 messages |
2007-08-23 15:56:40 | admin | create | |
|