Message 62664 - 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.

Author	loewis
Recipients	christian.heimes, giovannibajo, loewis
Date	2008-02-21.22:01:33
SpamBayes Score	0.008520164
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to	<[email protected]>

Content
> mbstowcs uses LC_CTYPE. Is that correct and consistent with the way > default encoding under UNIX is handled by Py3k? It's correct, but it's not consistent with the default encoding - there isn't really any default encoding in Py3k. More specifically, PyUnicode_FromString uses UTF-8, but not as a (changeable) default, but as part of its API specification. Command line arguments are in the locale's charset, so the LC_CTYPE must be used to convert them. > Would a Py_MainW or similar wrapper be easier on the UNIX guys? I'm just > asking, I don't have a definite idea. See above. The current POSIX implementation is incorrect also. It should use the locale's encoding, but doesn't.

> mbstowcs uses LC_CTYPE. Is that correct and consistent with the way
> default encoding under UNIX is handled by Py3k?

It's correct, but it's not consistent with the default encoding - there
isn't really any default encoding in Py3k. More specifically,
PyUnicode_FromString uses UTF-8, but not as a (changeable) default,
but as part of its API specification.
Command line arguments are in the locale's charset, so the LC_CTYPE
must be used to convert them.

> Would a Py_MainW or similar wrapper be easier on the UNIX guys? I'm just
> asking, I don't have a definite idea.

See above. The current POSIX implementation is incorrect also. It should
use the locale's encoding, but doesn't.

History
Date	User	Action	Args
2008-02-21 22:01:34	loewis	set	spambayes_score: 0.00852016 -> 0.008520164 recipients: + loewis, christian.heimes, giovannibajo
2008-02-21 22:01:33	loewis	link	issue2128 messages
2008-02-21 22:01:33	loewis	create