Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path: <d@davea.name>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.012
X-Spam-Evidence: '*H*': 0.98; '*S*': 0.00; 'cpython': 0.05; 'names.': 0.07; 'python': 0.08; 'to:addr:comp.lang.python': 0.09; 'files.': 0.09; 'am,': 0.12; 'library': 0.13; 'latter,': 0.16; 'released.': 0.16; 'cc:addr:python-list': 0.16; 'looked': 0.16; 'wrote:': 0.18; '(which': 0.19; "haven't": 0.20; 'maybe': 0.21; 'header:In-Reply- To:1': 0.22; "shouldn't": 0.23; 'uses.': 0.23; 'code': 0.25; 'windows': 0.26; 'cc:addr:gmail.com': 0.28; 'depends': 0.28; 'compile': 0.29; 'unicode': 0.29; 'cc:addr:python.org': 0.29; 'example': 0.29; "weren't": 0.30; 'least': 0.30; "isn't": 0.33; "won't": 0.33; 'header:User-Agent:1': 0.33; 'points': 0.34; 'dll': 0.34; 'fault': 0.34; 'issue': 0.35; 'file': 0.36; 'actively': 0.36; 'question': 0.36; 'cc:2**1': 0.36; 'encoding': 0.37; 'interface.': 0.37; 'but': 0.37; 'entry': 0.37; 'received:192': 0.37; 'think': 0.37; 'using': 0.38; 'some': 0.38; 'why': 0.39; 'received:192.168': 0.40; 'memory,': 0.67; 'supply': 0.69; 'header :Reply-To:1': 0.71; 'reply-to:no real name:2**0': 0.72; 'vista,': 0.84; 'xp,': 0.84; 'open,': 0.91
Date: Wed, 11 Jan 2012 06:45:43 -0500
From: Dave Angel <d@davea.name>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version: 1.0
To: comp.lang.python@googlegroups.com
Subject: Re: UnicodeEncodeError in compile
References: <9043309.329.1326169476466.JavaMail.geo-discussion-forums@yqhi24>	<jegrmo$juv$1@dough.gmane.org>	<mailman.4625.1326253880.27778.python-list@python.org> <9664479.1553.1326281266242.JavaMail.geo-discussion-forums@yqlp13>
In-Reply-To: <9664479.1553.1326281266242.JavaMail.geo-discussion-forums@yqlp13>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:+Mqes+5sihuEju4vj3QnEeCZD87sgshnJPZfIQHHMRt dU1POuUtItvPbdB9Gql1fiqcP4Cpy6LAvclkZmXXyZ/TcBfv+B zDyR/qmyoc9e1mNm+22e8ucHOa1/OnfmRQ3/MuP9613r9qyAox UMDmEkyiNZh523VPExp0CjRLWYDjmBkbiTRIzIrZBR19gJfBNq EqwSeHzfifBtnO9fg+4hpQHcsO7GRv7TgE++j7iORlt4frP0Sx V2JIznMMBsiJK9LwyihWiIavjeEX0e4NJJk4NA3c5a5tLDXoc7 Wiaw/S87FQo/Nes+J5qpLojihBqeb5DS6zX2qSTg8RMrCj2dEn 0BlCrdv1sD9QfJWZjzRI=
Cc: python-list@python.org, pyscripter@gmail.com
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: d@davea.name
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.4641.1326282354.27778.python-list@python.org>
Lines: 25
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1326282354 news.xs4all.nl 6883 [2001:888:2000:d::a6]:54078
X-Complaints-To: abuse@xs4all.nl
Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:18822

On 01/11/2012 06:27 AM, pyscripter@gmail.com wrote:
> <SNIP>
> Maybe the example of this question can be added to the issue 13785 as a proof that compile fails on valid file names.
>
> But I think the real issue is why on modern Windows systems the file system encoding is mbcs.  Shouldn't it be utf-16?
Depends what you mean by modern. The following isn't true for Windows 
95, 98, nor ME.  But they weren't modern when they were first released.

NT systems, (which includes Win2k, XP, Vista, and Win7)  for at least 
the last 15 years, have used Unicode for the file system.  They also 
supply an "ASCII" interface.  If Python is using the latter, then it 
won't be able to access all possible files.

Now, it may be the fault of the C library that CPython uses.  I haven't 
looked at any of the code for CPython.

This is all from memory, as I haven't actively used Windows for some 
time now.  But I think the DLL name is kernel32.dll, and the entry 
points have names like  CreateFileW() for the unicode open, and 
CreateFileA() for the "ASCII" open.

-- 

DaveA