[issue36354] Use CreateProcessW for Python 2.7 on Windows.

Gregory P. Smith added the comment: 2.7 was closed to new features eons ago. While subprocess32 backport might be a plausible home for this, I really can't handle doing anything significant for Windows within the confines of that project (it already makes me nervous that anyone is using

[issue36354] Use CreateProcessW for Python 2.7 on Windows.

Serhiy Storchaka added the comment: It is not enough to just replace CreateProcess with CreateProcessW. You will need to change also other related calls and resolve issues when you pass some arguments as 8-bit strings and other arguments as Unicode strings. You will need to backport a half

[issue36354] Use CreateProcessW for Python 2.7 on Windows.

Josh Rosenberg added the comment: 2.7 is in bug fix only mode, and even that ends at the end of this year. This seems more like a feature request than an actual bug; it works, but not great with Unicode in some cases (which describes large parts of Python 2). It does look like Python 3.7 at

[issue36354] Use CreateProcessW for Python 2.7 on Windows.

Terry J. Reedy added the comment: Is CreateProcessW already used in current 3.x? -- nosy: +terry.reedy ___ Python tracker ___ ___

[issue36354] Use CreateProcessW for Python 2.7 on Windows.

Ray Donnelly added the comment: .. and alternative to my ACP idea would be to use `GetACP()` or `getfilesystemencoding()` .. or? Suggestions welcome! -- ___ Python tracker

[issue36354] Use CreateProcessW for Python 2.7 on Windows.

New submission from Ray Donnelly : Hi all, I'd like to entertain some discussion around the idea of calling CreateProcessW instead of CreateProcess on Windows. I've written a patch as a proof of concept and I would love to get some feedback. I guess I've broken the normal