[issue36354] Use CreateProcessW for Python 2.7 on Windows.

[Gregory P. Smith]

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 subprocess32 on 
Windows at all).  

I don't intend to update subprocess32 with any new features at this point.

If you need an enhanced subprocess module for use on 2.7 on Windows I suggest 
creating your own fork/package for use in Anaconda 2.x distributions.

--
resolution:  -> rejected
stage:  -> resolved
status: open -> closed
type:  -> enhancement

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue36354] Use CreateProcessW for Python 2.7 on Windows.

[Serhiy Storchaka]

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 of Python 3. At end, this will break someones code.

The correct way to solve this issue -- upgrade to Python 3, where these issues 
were solved more smoothly and contsistently.

--
nosy: +serhiy.storchaka

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue36354] Use CreateProcessW for Python 2.7 on Windows.

[Josh Rosenberg]

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 least is using CreateProcessW already ( 
https://github.com/python/cpython/blob/3.7/Modules/_winapi.c#L1062 ), going 
along with the generally more Unicode-friendly vibe there.

The subprocess32 module on PyPI performed backports from Py3's subprocess to 
Py2 for POSIX systems; perhaps talk to the author (gregory.p.smith, whom I have 
nosied) about backporting similar improvements for the Windows side of the 
aisle?

--
nosy: +gregory.p.smith, josh.r

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue36354] Use CreateProcessW for Python 2.7 on Windows.

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Is CreateProcessW already used in current 3.x?

--
nosy: +terry.reedy

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue36354] Use CreateProcessW for Python 2.7 on Windows.

[Ray Donnelly]

Ray Donnelly  added the comment:

.. and alternative to my ACP idea would be to use `GetACP()` or 
`getfilesystemencoding()` .. or? Suggestions welcome!

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue36354] Use CreateProcessW for Python 2.7 on Windows.

[Ray Donnelly]

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 ACP/getfilesystemencoding() 
expectation for byte strings here. My idea to fix this was to use 
CreateProcessW only when all arguments (program name, arguments, cwd, 
environment) are unicode already.

The reason we'd like to use it on Anaconda Distribution is that we would like 
for conda to be able to handle Unicode as well as possible in as many 
situations as possible, including running a Python2 conda and creating conda 
envs with all sorts of glyphs in it.

We run into bug reports quite frequently from people who try to install 
Miniconda2 or Anaconda2 in their home directories due to their username 
containing certain codepoints.

--
files: 0017-Use-CreateProcessW-to-support-Unicode.patch
keywords: patch
messages: 338270
nosy: Ray Donnelly, giampaolo.rodola, paul.moore, steve.dower, tim.golden, 
zach.ware
priority: normal
severity: normal
status: open
title: Use CreateProcessW for Python 2.7 on Windows.
Added file: 
https://bugs.python.org/file48216/0017-Use-CreateProcessW-to-support-Unicode.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com