New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
subprocess under windows fails to quote properly when shell=True #46557
Comments
The subprocess.Popen function reorganises the command line for process Frankly I'm new to unittests and I more-or-less cloned an existing one |
You aren't testing the modified code, the Popen call should say I think that a more PEP-8-compliant style would be nice (removing the |
Gabriel Genellina wrote:
D'oh. Thanks, Gabriel. I'll rework the test and tidy |
Updated patch against r61514. Test code now PEP-8-compliant (I hope). New |
An up-to-date patch; same contents, but this one can be cleanly |
This is closely related to http://bugs.python.org/issue6689 |
Committed as r83830, r83831, r83832 |
Reverted because of test-breakage on unixes. |
ReComitted as r83947, r83956, r83957 and this time the buildbots look happy. (At least as regards this change). |
Is there any way to write code that's safe with or without this fix? If I have code that currently does this: subprocess.check_call('""c:\some path with spaces" arg1 arg2 "a quoted arg""', shell=True) ...will it break when running on a version of Python with this fix? Is there any good way to detect whether the running Python has this fix or not? |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: