Message 118268 - 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	ixokai, lemburg, loewis, pitrou, pjenvey, ronaldoussoren, vstinner
Date	2010-10-09.11:49:50
SpamBayes Score	1.0228531e-06
Marked as misclassified	No
Message-id	<4CB056DA.60006@v.loewis.de>
In-reply-to	<1286621540.3177.10.camel@localhost.localdomain>

Content
>> If the mere existence of the fsname encoding leads to that much >> confusion, I think I also support its removal. > > Well, the fsname encoding has a hardwired value under OS X (regardless > of the locale), which kind of justifies its existence, no? Perhaps. We could also declare that command line arguments and environment variables are always UTF-8-encoded on OSX (which I think would be fairly accurate), and stop relying on the locale to determine encodings on OSX (which Apple didn't like as a mechanism, anyway). I think OSX converges faster to UTF-8 than the other Unices.

>> If the mere existence of the fsname encoding leads to that much
>> confusion, I think I also support its removal.
> 
> Well, the fsname encoding has a hardwired value under OS X (regardless
> of the locale), which kind of justifies its existence, no?

Perhaps. We could also declare that command line arguments and
environment variables are always UTF-8-encoded on OSX (which I think
would be fairly accurate), and stop relying on the locale to determine
encodings on OSX (which Apple didn't like as a mechanism, anyway).
I think OSX converges faster to UTF-8 than the other Unices.

History
Date	User	Action	Args
2010-10-09 11:49:53	loewis	set	recipients: + loewis, lemburg, ixokai, ronaldoussoren, pitrou, vstinner, pjenvey
2010-10-09 11:49:51	loewis	link	issue9992 messages
2010-10-09 11:49:50	loewis	create