New submission from Akira Li:
$ TZ=:Europe/Moscow ./python -mtest -v test_time
======================================================================
FAIL: test_localtime_timezone (test.test_time.TestPytime)
----------------------------------------------------------------------
Traceback (most recent call last):
File ".../Lib/test/test_time.py", line 721, in test_localtime_timezone
self.assertEqual(lt.tm_gmtoff, -[time.timezone,
time.altzone][lt.tm_isdst])
AssertionError: 10800 != 14400
----------------------------------------------------------------------
Ran 45 tests in 1.832s
FAILED (failures=1, skipped=3)
test test_time failed
1 test failed:
test_time
UTC offset had changed on 2014-10-26 in Europe/Moscow timezone from
MSK+0400 to MSK+0300.
Python time.timezone returns -14400 (old utc offset) despite C timezone
variable having the correct value (Python uses tm_gmtoff from Jan here).
Similar case where timezone, altzone may be wrong
http://bugs.python.org/msg31138
The issue again http://bugs.python.org/issue22798 is that time timezone
attribute is out-of-sync with the corresponding C variable i.e., C
library provides correct values but time module doesn't use them.
----------
components: Library (Lib)
messages: 230684
nosy: akira
priority: normal
severity: normal
status: open
title: wrong time.timezone
type: behavior
versions: Python 3.4, Python 3.5, Python 3.6
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue22799>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
