New submission from Ray Donnelly <rdonne...@anaconda.com>:
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 <rep...@bugs.python.org> <https://bugs.python.org/issue36354> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
