UnicodeEncodeError in compile

[pyscripter at gmail.com]

On Wednesday, January 11, 2012 5:50:51 AM UTC+2, Terry Reedy wrote:
> On 1/10/2012 3:08 AM, Terry Reedy wrote:
> Is this a filename that could be an actual, valid filename on your system?

Yes it is. open works on that file.

> Good question. I believe this holdover from 2.x should be deleted.
> I argued that in http://bugs.python.org/issue10114
> (which was about a different problem) and now, directly, in
> http://bugs.python.org/issue13758
> 
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?