New submission from Patrick Storz <eduard.bra...@gmx.de>:
This is a follow-up to https://bugs.python.org/issue20010
I'm seeing this very issue in a recent gcc build of Python 3.8
(mingw-w64-x86_64-python 3.8.8-2 from MSYS2 project):
Python 3.8.8 (default, Feb 20 2021, 07:16:03) [GCC 10.2.0 64 bit (AMD64)] on
win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import time
>>> time.strftime('%z', time.localtime(time.time()))
'Mitteleuropäische Sommerzeit'
>>> time.strftime('%Z', time.localtime(time.time()))
'Mitteleuropäische Sommerzeit'
If this is indeed fixed in MSVCRT, it seems behavior is still not guaranteed
when compiling with mingw-w64 gcc.
----------
components: Library (Lib), Windows
messages: 389641
nosy: Aaron.Meurer, Ede123, Václav Dvořák, civalin, docs@python, eryksun,
ezio.melotti, kepkin, martin-t, paul.moore, r.david.murray, steve.dower,
tim.golden, vstinner, zach.ware
priority: normal
severity: normal
status: open
title: time.strftime('%z') doesn't return UTC offset in the form ±HHMM
type: behavior
versions: Python 3.8
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue43649>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
