[issue20042] Python Launcher, Windows, fails on scripts w/ non-latin names

2017-07-05 Thread Terry J. Reedy
Changes by Terry J. Reedy : -- resolution: -> out of date stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue20042] Python Launcher, Windows, fails on scripts w/ non-latin names

2017-07-05 Thread Konstantin Zemlyak
Konstantin Zemlyak added the comment: Terry J. Reedy wrote: > Is this still relevant or should it be closed? Should be closed. > On Win10, I created a short script юникод.py using Save As from IDLE. > > py -2 юникод.py produces > C:\Programs\Python27\python.exe: can't open file '??.py':

[issue20042] Python Launcher, Windows, fails on scripts w/ non-latin names

2017-07-05 Thread Terry J. Reedy
Terry J. Reedy added the comment: Is this still relevant or should it be closed? On Win10, I created a short script юникод.py using Save As from IDLE. py -2 юникод.py produces C:\Programs\Python27\python.exe: can't open file '??.py': [Errno 22] Invalid argument If the patch fixes 2.7 and

[issue20042] Python Launcher, Windows, fails on scripts w/ non-latin names

2015-04-23 Thread Mark Lawrence
Mark Lawrence added the comment: The bug reported in msg225529 has been fixed, but there's another one a few lines up https://hg.python.org/cpython/file/bd656916586f/PC/launcher.c#l265 as there's only one % but two parameters. Although IIRC we'd get away with this the way C works, shouldn't

[issue20042] Python Launcher, Windows, fails on scripts w/ non-latin names

2014-08-19 Thread eryksun
eryksun added the comment: The problem is skip_whitespace mistakenly calls isspace instead of iswspace. http://hg.python.org/cpython/file/c0e311e010fc/PC/launcher.c#l48 isspace has undefined behavior when the argument is not EOF or in the range of 0 through 0xFF:

[issue20042] Python Launcher, Windows, fails on scripts w/ non-latin names

2014-08-18 Thread Steve Dower
Steve Dower added the comment: It should be fixable. In general, Unicode in the console is fine, but the CRT doesn't handle it well (as shown by the _setmode extension being able to fix it). The 'correct' fix for Unicode in the console is at http://www.siao2.com/2010/04/07/9989346.aspx and

[issue20042] Python Launcher, Windows, fails on scripts w/ non-latin names

2014-08-10 Thread Mark Lawrence
Mark Lawrence added the comment: Is this actually fixable? I only ask as we seem to have a whole lot of fun with anything involving cmd.exe as epitomized on #1602. -- nosy: +BreamoreBoy, steve.dower, vinay.sajip, zach.ware -brian.curtin versions: +Python 2.7, Python 3.4, Python 3.5

[issue20042] Python Launcher, Windows, fails on scripts w/ non-latin names

2014-02-28 Thread Martin Dengler
Changes by Martin Dengler mar...@martindengler.com: -- nosy: +mdengler ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20042 ___ ___

[issue20042] Python Launcher, Windows, fails on scripts w/ non-latin names

2013-12-27 Thread Terry J. Reedy
Changes by Terry J. Reedy tjre...@udel.edu: -- title: Python Launcher for Windows fails to invoke scripts with non-latin names - Python Launcher, Windows, fails on scripts w/ non-latin names ___ Python tracker rep...@bugs.python.org