The results of time.tzname print broken.

[maxtortime]

BPO	34135
Nosy	@pfmoore, @tjguk, @zware, @zooba, @maxtortime, @tirkarthi, @iritkatriel

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2022-01-17.10:42:37.978>
created_at = <Date 2018-07-17.04:52:03.610>
labels = ['type-bug', 'OS-windows']
title = 'The results of time.tzname print broken.'
updated_at = <Date 2022-01-17.10:42:37.978>
user = 'https://github.com/maxtortime'

bugs.python.org fields:

activity = <Date 2022-01-17.10:42:37.978>
actor = 'iritkatriel'
assignee = 'none'
closed = True
closed_date = <Date 2022-01-17.10:42:37.978>
closer = 'iritkatriel'
components = ['Windows']
creation = <Date 2018-07-17.04:52:03.610>
creator = 'maxtortime'
dependencies = []
files = []
hgrepos = []
issue_num = 34135
keywords = []
message_count = 3.0
messages = ['321790', '321809', '400708']
nosy_count = 7.0
nosy_names = ['paul.moore', 'tim.golden', 'zach.ware', 'steve.dower', 'maxtortime', 'xtreak', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue34135'
versions = ['Python 2.7', 'Python 3.5']

[maxtortime]

When I call time.tzname at Korean Windows. (Microsoft Windows 10 Pro(10.0.17134 Build 17134))

It prints like below. This problem occurred Python 2 and 3 both.
>>> import time
>>> time.tzname
('´ëÇѹα¹ Ç¥ÁؽÃ', '´ëÇѹα¹ Àϱ¤ Àý¾à ½Ã°£')

I used chardet for getting correct tzname.
>>> import chardet
>>> tzname = [tzn.encode('latin-1').decode('cp949') for tzn in time.tzname]
>>> tzname
['대한민국 표준시', '대한민국 일광 절약 시간']

I think that cause of this problem is tzname encoded by 'latin-1' at Window s.

[tirkarthi]

There is some discussion about this at https://bugs.python.org/issue16322#msg251068 and seems the issue is a related one.

Thanks

[iritkatriel]

bpo-16322 was closed as a duplicate of bpo-36779 which was fixed. Does that resolve this problem as well?