This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/4033] mktime bug in Europe/Lisbon timezone
- From: "sergio at sergiomb dot no-ip dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 5 Mar 2008 02:52:10 -0000
- Subject: [Bug libc/4033] mktime bug in Europe/Lisbon timezone
- References: <20070213141801.4033.cvalente@spambob.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From sergio at sergiomb dot no-ip dot org 2008-03-05 02:52 -------
ok as you write the bug could be I my expectations :
as datetest.py
import time
print time.mktime((1970, 1, 1, 0, 0, 0, 3, 1, 0))
TZ='WET' python -u datetest.py
0.0
TZ='WEST' python -u datetest.py
0.0
TZ='Europe/London' python -u datetest.py
-3600.0
TZ='Europe/Lisbon' python -u datetest.py
-3600.0
TZ='America/Caracas' python -u datetest.py
14400.0
TZ='America/Caracas' date
Tue Mar 4 22:01:33 VET 2008
TZ='VET' python -u datetest.py
0.0
TZ='Atlantic/Cape_Verde' date
Wed Mar 5 01:33:25 CVT 2008
TZ='CVT' date
Wed Mar 5 02:34:00 CVT 2008
so setting TZ with country is different to setting TZ with 3 letters of the same
timezone ?
This is the bug or a very odd feature, this is not, a result as I expect, and
not a bug specifically in my timezone ...
--
http://sourceware.org/bugzilla/show_bug.cgi?id=4033
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.