-
Notifications
You must be signed in to change notification settings - Fork 1
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
Popen should use a sequence of command line arguments, not a string. #508
Comments
Author: justinc The parts of this ticket that are known to impact us are resolved in r2444 and the fix for #505. |
Author: cemeyer |
Author: cemeyer Note: there is one place in windows_api.py where I couldn't find a way to use the sequence-style Popen invocation because of the way subprocess works on Windows. |
Author: cemeyer |
Author: cemeyer It looks like softwareupdater already uses Popen correctly. There are a few uses of the depricated form of popen, but none of them are in nodemanager/softwareupdater/repy:
There are several uses of os.system, again none of which are in "critical" places (repy, nodemanager, softwareupdater):
|
Author: cemeyer |
We are using subprocess.Popen() with a string based argument in many places. Suppose we want to run the command:
ls -l
, we commonly call this like:subprocess.Popen('ls -l')
This actually causes us problems when the command or arguments may have spaces. To avoid any potential problems, we should instead use the 'sequence' form. This looks like the following:
subprocess.Popen('-l')
This seems to be the root cause of #505
The text was updated successfully, but these errors were encountered: