[issue762963] timemodule.c: Python loses current timezone

Changes by Alexander Belopolsky : -- resolution: -> out of date status: open -> closed superseder: -> Time zone-capable variant of time.localtime ___ Python tracker

[issue762963] timemodule.c: Python loses current timezone

Changes by Brett Cannon br...@python.org: -- nosy: -brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue762963 ___ ___ Python-bugs-list

[issue762963] timemodule.c: Python loses current timezone

Stephen White stephen-python@randomstuff.org.uk added the comment: Debian appear to have applied this patch, and it seems to be causing problems: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593461 -- nosy: +Stephen.White ___ Python tracker

[issue762963] timemodule.c: Python loses current timezone

Changes by Jon Siddle j...@corefiling.co.uk: -- nosy: +jonsiddle ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue762963 ___ ___ Python-bugs-list

[issue762963] timemodule.c: Python loses current timezone

Stephen White stephen-python@randomstuff.org.uk added the comment: The patch, issue762963.diff, is broken. It is calling mktime on a struct tm that is initialized to zeros. This means that it should be filling in the missing fields based on their correct values for the date 1st Jan 1900,

[issue762963] timemodule.c: Python loses current timezone

Paul Boddie p...@boddie.org.uk added the comment: I don't understand how this bug and its patches are still active. It's difficult for me to remember what I was doing in early 2007 when I started working on issue #1667546, but I can well imagine that it was in response to this and a number of

[issue762963] timemodule.c: Python loses current timezone

Alexander Belopolsky belopol...@users.sourceforge.net added the comment: I agree with Martin. A proper fix would be to use tm_gmtoff explicitly where available and carry it in time.struct_time. See issue1647654 and issue4086. Interestingly, the issue does not show up on OSX, which being a

[issue762963] timemodule.c: Python loses current timezone

Alexander Belopolsky belopol...@users.sourceforge.net added the comment: Another related issue is issue1667546. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue762963 ___

[issue762963] timemodule.c: Python loses current timezone

Changes by Alexander Belopolsky belopol...@users.sourceforge.net: -- nosy: +belopolsky ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue762963 ___

[issue762963] timemodule.c: Python loses current timezone

Grant Bowman grant...@gmail.com added the comment: Is there anything others like me can do to help get this fixed? -- nosy: +grantbow ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue762963 ___

[issue762963] timemodule.c: Python loses current timezone

R. David Murray rdmur...@bitdance.com added the comment: Review the code, test the patch, confirm that it fixes the problem and doesn't break anything else, and report your results here. That doesn't guarantee that it will get applied, but it definitely helps. -- nosy:

[issue762963] timemodule.c: Python loses current timezone

Paul Boddie p...@boddie.org.uk added the comment: Well, this still doesn't work for me. I'm running Kubuntu 8.04 (libc6 package version 2.7-10ubuntu5) and reside in the CEST time zone, yet attempting to display the time zone always seems to give +. Here are the failing tests, too:

[issue762963] timemodule.c: Python loses current timezone

Brian Curtin cur...@acm.org added the comment: Here's an updated version of the previous patches with the test included in test_time.py. The test fails on Linux before the timemodule.c file is changed, then it passes once applied. -- keywords: +needs review nosy: +brian.curtin stage:

[issue762963] timemodule.c: Python loses current timezone

Changes by Christian Heimes: -- versions: +Python 2.5, Python 2.6 Tracker [EMAIL PROTECTED] http://bugs.python.org/issue762963 ___ Python-bugs-list mailing list