Message 105008 - 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	vstinner
Recipients	Arfrever, lemburg, loewis, pitrou, vstinner
Date	2010-05-05.09:31:03
SpamBayes Score	0.0006495079
Marked as misclassified	No
Message-id	<1273051865.07.0.321860913525.issue8610@psf.upfronthosting.co.za>
In-reply-to

Content
> I think that using ASCII is a safer choice in case of errors. I choosed UTF-8 to keep backward compatibility: PyUnicode_DecodeFSDefaultAndSize() uses utf-8 if Py_FileSystemDefaultEncoding==NULL. If the OS has no nl_langinfo(CODESET) function at all, Python3 uses utf-8. > Using UTF-8 may be safe for reading file names, but it's not > safe for creating files or directories. Well, I don't know. You are maybe right. And which encoding should be used if nl_langinfo(CODESET) function is missing: ASCII or UTF-8? UTF-8 is also an optimist choice: I bet that more and more OS will move to UTF-8.

> I think that using ASCII is a safer choice in case of errors.

I choosed UTF-8 to keep backward compatibility: PyUnicode_DecodeFSDefaultAndSize() uses utf-8 if Py_FileSystemDefaultEncoding==NULL. If the OS has no nl_langinfo(CODESET) function at all, Python3 uses utf-8.

> Using UTF-8 may be safe for reading file names, but it's not
> safe for creating files or directories.

Well, I don't know. You are maybe right. And which encoding should be used if nl_langinfo(CODESET) function is missing: ASCII or UTF-8?

UTF-8 is also an optimist choice: I bet that more and more OS will move to UTF-8.

History
Date	User	Action	Args
2010-05-05 09:31:05	vstinner	set	recipients: + vstinner, lemburg, loewis, pitrou, Arfrever
2010-05-05 09:31:05	vstinner	set	messageid: <1273051865.07.0.321860913525.issue8610@psf.upfronthosting.co.za>
2010-05-05 09:31:03	vstinner	link	issue8610 messages
2010-05-05 09:31:03	vstinner	create