Message 116390 - 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	eric.araujo, tarek, vstinner, zegreek
Date	2010-09-14.12:02:44
SpamBayes Score	6.1495253e-13
Marked as misclassified	No
Message-id	<1284465781.34.0.139733824908.issue6011@psf.upfronthosting.co.za>
In-reply-to

Content
For non-ascii directory name but ascii locale (eg. C locale), we have 3 choices: a- read Makefile as a binary file b- use the PEP 383 c- refuse to compile (a) doesn't seem easy because it looks like distutils use the unicode type for all paths. (b) supposes to patch distutils to ensure that reading (and writing?) Makefile uses errors='surrogateescape'. About (c), it can be a temporary solution. But I also think that non-ascii directory name and ascii locale encoding is a rare use case.

For non-ascii directory name but ascii locale (eg. C locale), we have 3 choices:
 a- read Makefile as a binary file
 b- use the PEP 383
 c- refuse to compile

(a) doesn't seem easy because it looks like distutils use the unicode type for all paths. (b) supposes to patch distutils to ensure that reading (and writing?) Makefile uses errors='surrogateescape'.

About (c), it can be a temporary solution. But I also think that non-ascii directory name and ascii locale encoding is a rare use case.

History
Date	User	Action	Args
2010-09-14 12:03:01	vstinner	set	recipients: + vstinner, tarek, eric.araujo, zegreek
2010-09-14 12:03:01	vstinner	set	messageid: <1284465781.34.0.139733824908.issue6011@psf.upfronthosting.co.za>
2010-09-14 12:02:45	vstinner	link	issue6011 messages
2010-09-14 12:02:44	vstinner	create