Message 311721 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

In-reply-to
Author	methane
Recipients	cypressyew, methane
Date	2018年02月06日.09:39:42
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1517909982.7.0.467229070634.issue32781@psf.upfronthosting.co.za>

Content
> But even so, I think this bug is still valid, as the lzh_TW does not exist in the lib at all. Python doesn't have locale database, while have some aliases. Python uses libc's locale. This exception is raised because `_parse_localename` doesn't support locale name without encoding. In case of zh_TW, alias is registered: 'zh_tw': 'zh_TW.big5', But I don't think adding `lzh_tw` to alias is good idea. There are no "one right alias table". In case of zh_tw, you may want zh_TW.UTF-8 rather than zh_TW.bit5, don't you? So I think supporting locale name without encoding is right way. Maybe, we should return None for encoding in such situation.

Content

> But even so, I think this bug is still valid, as the lzh_TW does not exist in the lib at all.
Python doesn't have locale database, while have some aliases.
Python uses libc's locale.
This exception is raised because `_parse_localename` doesn't support
locale name without encoding.
In case of zh_TW, alias is registered:
 'zh_tw': 'zh_TW.big5',
But I don't think adding `lzh_tw` to alias is good idea.
There are no "one right alias table". In case of zh_tw, you may
want zh_TW.UTF-8 rather than zh_TW.bit5, don't you?
So I think supporting locale name without encoding is right way.
Maybe, we should return None for encoding in such situation.

History
Date	User	Action	Args
2018年02月06日 09:39:42	methane	set	recipients: + methane, cypressyew
2018年02月06日 09:39:42	methane	set	messageid: <1517909982.7.0.467229070634.issue32781@psf.upfronthosting.co.za>
2018年02月06日 09:39:42	methane	link	issue32781 messages
2018年02月06日 09:39:42	methane	create

homepage