[issue13466] new timezones

2015-10-02 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Since nobody responded, I am closing this issue. -- resolution: -> out of date status: open -> closed ___ Python tracker ___

[issue13466] new timezones

2015-08-28 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Since Russia has fixed this bug legislatively last year, can we close the issue now? http://www.theguardian.com/world/2014/jul/01/russia-state-duma-daylight-saving-time-summer -- ___ Python tracker

[issue13466] new timezones

2011-11-26 Thread Arfrever Frehtes Taifersar Arahesis
Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue13466] new timezones

2011-11-24 Thread Marc-Andre Lemburg
Marc-Andre Lemburg added the comment: Amaury Forgeot d'Arc wrote: > > Amaury Forgeot d'Arc added the comment: > >>> But that does not give the *other* timezone :-( >> Which other timezone ? > I meant the other timezone *name*. > > I think we don't understand each other: > - time.timezone is

[issue13466] new timezones

2011-11-24 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc added the comment: > > But that does not give the *other* timezone :-( > Which other timezone ? I meant the other timezone *name*. I think we don't understand each other: - time.timezone is the offset of the local (non-DST) timezone. - time.altzone is the offset of local DS

[issue13466] new timezones

2011-11-24 Thread Marc-Andre Lemburg
Marc-Andre Lemburg added the comment: Amaury Forgeot d'Arc wrote: > > Amaury Forgeot d'Arc added the comment: > >> A fairly "correct" way is to query the time zone database at time module >> import time by using the DST and GMT offset of that time. > > But that does not give the *other* time

[issue13466] new timezones

2011-11-23 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc added the comment: Another way to fix the issue is to wait 40 days. There won't be any release in-between anyway! -- ___ Python tracker ___ __

[issue13466] new timezones

2011-11-23 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc added the comment: > A fairly "correct" way is to query the time zone database at time module > import time by using the DST and GMT offset of that time. But that does not give the *other* timezone :-( > IMO time.timezone and time.daylight should be deprecated since they >

[issue13466] new timezones

2011-11-23 Thread Marc-Andre Lemburg
Marc-Andre Lemburg added the comment: Amaury Forgeot d'Arc wrote: > > The error comes from the way Python computes timezone and daylight: it > queries the tm_gmtoff of two timestamps, one close to the first of January, > the other close to the first of July. But last January the previous >

[issue13466] new timezones

2011-11-23 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc added the comment: On my Ubuntu machine, I get: $ zdump -v Europe/Moscow | grep 201[0-9] Europe/Moscow Sat Mar 27 22:59:59 2010 UTC = Sun Mar 28 01:59:59 2010 MSK isdst=0 gmtoff=10800 Europe/Moscow Sat Mar 27 23:00:00 2010 UTC = Sun Mar 28 03:00:00 2010 MSD isdst=1 gmto

[issue13466] new timezones

2011-11-23 Thread Ezio Melotti
Changes by Ezio Melotti : -- components: +Extension Modules nosy: +belopolsky, lemburg stage: -> test needed versions: +Python 3.2, Python 3.3 ___ Python tracker ___ ___

[issue13466] new timezones

2011-11-23 Thread Aleksey
New submission from Aleksey : Hi Guys, Since 31 august 2011 in Russian Federation always DST time. http://worldtimezone.net/dst_news/dst_news_russia36.html But >>> time.tzname ('MSK', 'MSK') >>> time.localtime().tm_isdst 0 >>> time.timezone -10800 >>> time.altzone -14400 i think tm_isdst must b