[Mailman-Developers] clobber_date bug
Dan Mick <dmick@utopia.West.Sun.COM>
Thu, 8 Nov 2001 14:23:58 -0800 (PST)
> > While clobber_date doesn't process the existing date, it
> > seems to replace it by the local date (namely
> > the output of ctime(time()). That seems correct to me.
> > Are you certain your local TZ is set properly?
> Using python 1.5.2, ctime() is giving local time without timezone info.
Good point. It's the correct time, but it's not fully-qualified.
I get it.
> If I use asctime(gmtime(time)) I seem to get the correct result.
> [eds@ike eds]$ python
> Python 1.5.2 (#1, Dec 21 2000, 15:29:08) [GCC egcs-2.91.66
> 19990314/Linux (egcs- on linux-i386
> Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam
> >>> time.ctime(time.time())
> 'Thu Nov 8 16:01:44 2001'
> >>> time.tzname
> ('CST', 'CDT')
> >>> time.timezone /3600
> >>> time.asctime(time.gmtime(time.time()))
> 'Thu Nov 8 22:06:05 2001'
Well, sorta. You really want that TZ information appended.
> So it looks like my options are to use asctime(gmtime(time)) or write a
> routine that parses time.timezone into "-0600".
Luckily 'altzone' is defined in time, so
"+%02d%02d" % (time.altzone / 3600, time.altzone % 3600)
seems to do it. But it sure looks like a bug to me.