New submission from Evan Andrews:
The method used for spawning subprocesses on Windows is not thread-safe under
certain circumstances. The following example demonstrates how this manifests:
>>> import threading
>>> import subprocess
>
Evan Andrews added the comment:
Thanks, Vinay. I understand you're busy, and I'm in no particular rush to have
this looked at, so feel free to come back to it when you have more time. I've
submitted the changes as a PR.
I also have an additional concern - even with this change
Changes by Evan Andrews <evanundersc...@gmail.com>:
--
pull_requests: +2134
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue28595>
___
Evan Andrews added the comment:
Do I need to create a pull request for this?
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Evan Andrews added the comment:
Unfortunately shlex.shlex's defaults are probably going to remain that way for
a long time in order to avoid breaking backwards compatibility. Presumably
shlex.split was added so you didn't have to remember to set posix and
whitespace_split yourself
Evan Andrews added the comment:
Attaching an updated patch now that the two linked issues are resolved.
--
Added file: http://bugs.python.org/file46335/shlex2.diff
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
