➜

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 BreamoreBoy, ezio.melotti, flox, joe.amenta, jvr, loewis, r.david.murray, vstinner
Date 2010-09-12.16:36:10
SpamBayes Score 2.6449156e-06
Marked as misclassified No
Message-id <4C8D0177.7080803@v.loewis.de>
In-reply-to <1284165433.49.0.234813791168.issue767645@psf.upfronthosting.co.za>
Content 
> I think that supports_unicode_filenames is still useful to check if
> the filesystem API uses bytes (Linux, FreeBSD, Solaris, ...) or
> characters (Mac OS X, Windows). Mac OS X is a special case because
> the C API uses char* (byte string), but the filesystem encoding is
> fixed to utf-8 and it doesn't accept invalid utf-8 filenames. So I
> would like to say that supports_unicode_filenames should be True on
> Mac OS X (which was the initial request).

Sounds reasonable.
History
Date User Action Args
2010-09-12 16:36:12loewissetrecipients: + loewis, jvr, vstinner, ezio.melotti, r.david.murray, joe.amenta, flox, BreamoreBoy
2010-09-12 16:36:11loewislinkissue767645 messages
2010-09-12 16:36:10loewiscreate