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, eric.araujo, lemburg, pitrou, vstinner
Date 2010-09-07.23:30:38
SpamBayes Score 3.6833313e-07
Marked as misclassified No
Message-id <1283902241.08.0.27605573041.issue9632@psf.upfronthosting.co.za>
In-reply-to
Content
"keep the C function"

Hum, currently, Python3 only has a *private* function called _Py_SetFileSystemEncoding() which can only be called after _Py_InitializeEx() (because it relies on the codecs API). If you consider that there is a real use case, we should create a function to set the filesystem encoding, function that should (have to?) be called before Py_InitializeEx().

I still think that Python knows better than the application how to set the encoding (when, how to choose it, etc.).
History
Date User Action Args
2010-09-07 23:30:41vstinnersetrecipients: + vstinner, lemburg, pitrou, eric.araujo, Arfrever
2010-09-07 23:30:41vstinnersetmessageid: <1283902241.08.0.27605573041.issue9632@psf.upfronthosting.co.za>
2010-09-07 23:30:38vstinnerlinkissue9632 messages
2010-09-07 23:30:38vstinnercreate