[Python-Dev] PEP 383: Non-decodable Bytes in System Character Interfaces (original) (raw)
Piet van Oostrum piet at cs.uu.nl
Sun May 17 21:47:16 CEST 2009
- Previous message: [Python-Dev] LZW support in tarfile ?
- Next message: [Python-Dev] PEP 384: Defining a Stable ABI
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ned Deily <nad at acm.org> (ND) wrote:
ND> In article <m2ocueq6mm.fsf at cs.uu.nl>, Piet van Oostrum <piet at cs.uu.nl> ND> wrote:
>>>>> Ronald Oussoren <ronaldoussoren at mac.com> (RO) wrote: >RO> For what it's worth, the OSX API's seem to behave as follows: >RO> * If you create a file with an non-UTF8 name on a HFS+ filesystem the >RO> system automaticly encodes the name.
>RO> That is, open(chr(255), 'w') will silently create a file named '%FF' >RO> instead of the name you'd expect on a unix system. Not for me (I am using Python 2.6.2). >>> f = open(chr(255), 'w') Traceback (most recent call last): File "", line 1, in IOError: [Errno 22] invalid mode ('w') or filename: '\xff' >>>
ND> What version of OSX are you using? On Tiger 10.4.11 I see the failure ND> you see but on Leopard 10.5.6 the behavior Ronald reports.
Yes, I am using Tiger (10.4.11). Interesting that it has changed on Leopard.
Piet van Oostrum <piet at cs.uu.nl> URL: http://pietvanoostrum.com [PGP 8DAE142BE17999C4] Private email: piet at vanoostrum.org
- Previous message: [Python-Dev] LZW support in tarfile ?
- Next message: [Python-Dev] PEP 384: Defining a Stable ABI
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]