[issue19264] subprocess.Popen doesn't support unicode on Windows

2017-03-15 Thread Valentin LAB
Valentin LAB added the comment: For eventual other people wanting a workaround, this is the code I used to leverage ``ctypes`` and redo what last python 3 code is doing. Any comment are welcome, this is my first go at ``ctypes``. I didn't extensively tested the code... so use at your own risk.

[issue19264] subprocess.Popen doesn't support unicode on Windows

2014-03-25 Thread Terry J. Reedy
Changes by Terry J. Reedy : -- resolution: -> wont fix stage: test needed -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue19264] subprocess.Popen doesn't support unicode on Windows

2014-03-25 Thread STINNER Victor
STINNER Victor added the comment: > The original issue was reported against 2.7 Oh... Ok :-) It's tricky to fix this issue in Python 2.7 because you have to choose which function is used: CreateProcessA() (bytes) or CreateProcessW() (Unicode). To use CreateProcessW(), you have to decode byte

[issue19264] subprocess.Popen doesn't support unicode on Windows

2014-03-22 Thread Terry J. Reedy
Terry J. Reedy added the comment: You're right, the bug/enhancement border for 2.7 unicode issues has been shifted a bit (or perhaps made a bit more consistent). A failing case is still needed. -- type: enhancement -> behavior ___ Python tracker

[issue19264] subprocess.Popen doesn't support unicode on Windows

2014-03-22 Thread Martin v . Löwis
Martin v. Löwis added the comment: The issue is really that Terry had removed 2.7 from the list of affected versions, and added 3.4 instead. The original issue was reported against 2.7, where the observation that it uses CreateProcess is correct: http://hg.python.org/cpython/file/babb9479b79f/

[issue19264] subprocess.Popen doesn't support unicode on Windows

2014-03-22 Thread STINNER Victor
STINNER Victor added the comment: I don't understand this issue. Python 3 uses CreateProcessW() and so support the full Unicode range. I suggest to close this issue as invalid. Popen() parameters are Unicode strings. It may support bytes string, but passing bytes to OS functions on Windows is de

[issue19264] subprocess.Popen doesn't support unicode on Windows

2014-03-22 Thread Terry J. Reedy
Terry J. Reedy added the comment: Peter, can you post 1 or more failing examplex? With some, I might be persuaded that this is a bug. Victor, I know you have worked in this area. Any opinions? -- nosy: +haypo stage: -> test needed versions: +Python 3.5 __

[issue19264] subprocess.Popen doesn't support unicode on Windows

2014-03-22 Thread akira
akira added the comment: I've checked the source code for 3.4; `subprocess` uses `_winapi.CreateProcess` on Windows [1] that in turn uses `CreateProcessW` [2]. CreateProcessA is not used. `Popen` should already support Unicode on Windows though I don't see explicit tests for non-ascii argumen

[issue19264] subprocess.Popen doesn't support unicode on Windows

2013-10-18 Thread Terry J. Reedy
Terry J. Reedy added the comment: The docs say that args should be a string or sequence of strings. It also says "On Windows, the class uses the Windows CreateProcess() function.", so it is not a bug for it to do that. However, CreateProcessW sounds like a good (and overdue, and overlooked) en

[issue19264] subprocess.Popen doesn't support unicode on Windows

2013-10-14 Thread Peter Graham
New submission from Peter Graham: On Windows, subprocess.Popen requires the executable name and working directory to be ascii. This is because it calls CreateProcess instead of CreateProcessW. -- components: Library (Lib), Unicode, Windows messages: 199976 nosy: ezio.melotti, peter0 pr