[issue20042] Python Launcher for Windows fails to invoke scripts with non-latin names

2013-12-21 Thread Konstantin Zemlyak
New submission from Konstantin Zemlyak: Running `py.exe юникод.py` in cmd window fails: E:\set PYLAUNCH_DEBUG=1 E:\py юникод.py launcher build: 32bit launcher executable: Console File 'C:\Users\Zart\AppData\Local\py.ini' non-existent Using global configuration file 'C:\Windows\py.ini' Called

[issue20042] Python Launcher for Windows fails to invoke scripts with non-latin names

2013-12-21 Thread Konstantin Zemlyak
Changes by Konstantin Zemlyak z...@zartsoft.ru: Removed file: http://bugs.python.org/file33247/pylauncher-fix-launcing-unicode-filenames.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20042

[issue20042] Python Launcher for Windows fails to invoke scripts with non-latin names

2013-12-21 Thread Konstantin Zemlyak
Konstantin Zemlyak added the comment: Sorry, fixed whitespaces in the patch. -- Added file: http://bugs.python.org/file33248/pylauncher-fix-launcing-unicode-filenames.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20042

[issue20042] Python Launcher for Windows fails to invoke scripts with non-latin names

2013-12-21 Thread STINNER Victor
STINNER Victor added the comment: It looks like the wide character strings (wchar_t*) are misused. For example: error(RC_NO_PYTHON, LRequested Python version (%s) ..., p[1]); fwprintf(stdout, Lusage: %s ...\n\n, argv[0]); The %s formatter is for byte string (char*), %ls should be used instead.

[issue20042] Python Launcher for Windows fails to invoke scripts with non-latin names

2013-12-21 Thread STINNER Victor
Changes by STINNER Victor victor.stin...@gmail.com: -- nosy: +brian.curtin, loewis, tim.golden ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20042 ___

[issue20042] Python Launcher for Windows fails to invoke scripts with non-latin names

2013-12-21 Thread Konstantin Zemlyak
Konstantin Zemlyak added the comment: I don't care much about debug output though it probably should be fixed. The point is that changing text mode of stdout has a weird side effect of fixing command-line arguments when invoking interactively from cmd.exe. --

[issue20042] Python Launcher for Windows fails to invoke scripts with non-latin names

2013-12-21 Thread Antoine Pitrou
Changes by Antoine Pitrou pit...@free.fr: -- stage: - patch review versions: +Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20042 ___

[issue20042] Python Launcher for Windows fails to invoke scripts with non-latin names

2013-12-21 Thread Konstantin Zemlyak
Konstantin Zemlyak added the comment: There is something weird with my proposed fix. Right after submitting a bug with patch I've updated pythons on my system - 2.7.5 to 2.7.6, 3.3.2 to 3.3.3, and installed 3.4.0b1 - both 32- and 64-bit. Then my fixed py.exe stopped working. Then I've added

[issue20042] Python Launcher for Windows fails to invoke scripts with non-latin names

2013-12-21 Thread Konstantin Zemlyak
Konstantin Zemlyak added the comment: Some more fun stuff with command-line (I'm cutting output to few essential lines for easier reading): e:\cpython\PCbuild\py.exe юникод.py ... Called with command line: .py run_child: about to run 'C:\Program Files (x86)\Python33\python.exe .py' C:\Program