This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Ray Donnelly
Recipients Ray Donnelly, giampaolo.rodola, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-03-18.17:45:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1552931150.38.0.949997697038.issue36354@roundup.psfhosted.org>
In-reply-to
Content
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.
History
Date User Action Args
2019-03-18 17:45:50Ray Donnellysetrecipients: + Ray Donnelly, paul.moore, giampaolo.rodola, tim.golden, zach.ware, steve.dower
2019-03-18 17:45:50Ray Donnellysetmessageid: <1552931150.38.0.949997697038.issue36354@roundup.psfhosted.org>
2019-03-18 17:45:50Ray Donnellylinkissue36354 messages
2019-03-18 17:45:50Ray Donnellycreate