RetroSearch Browse

Thu Apr 30 21:33:05 CEST 2009 · https://mail.python.org/pipermail/python-dev/2009-April/089295.html

>>>>> 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 "<stdin>", line 1, in <module>
IOError: [Errno 22] invalid mode ('w') or filename: '\xff'
>>> 

I once got a tar file from a Linux system which contained a file with a
non-ASCII, ISO-8859-1 encoded filename. The tar file refused to be
unpacked on a HFS+ filesystem.
-- 
Piet van Oostrum <piet at cs.uu.nl>
URL: http://pietvanoostrum.com [PGP 8DAE142BE17999C4]
Private email: piet at vanoostrum.org

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2009-April/089295.html below:

Non-decodable Bytes in System Character Interfaces