[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

miss-islington added the comment: New changeset ec3839a215a68cf35ff1f90cb6823f67a5abdce3 by Miss Islington (bot) in branch '3.8': bpo-6689: os.path.commonpath raises ValueError for different drives isn't documented (GH-14045)

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

Change by miss-islington : -- pull_requests: +13920 pull_request: https://github.com/python/cpython/pull/14058 ___ Python tracker ___

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

miss-islington added the comment: New changeset 95492032c48fef20b9c7076a23fe7e46927a4688 by Miss Islington (bot) (Makdon) in branch 'master': bpo-6689: os.path.commonpath raises ValueError for different drives isn't documented (GH-14045)

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

Change by Roundup Robot : -- pull_requests: +13907 pull_request: https://github.com/python/cpython/pull/14045 ___ Python tracker ___

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

Changes by Mark Lawrence breamore...@yahoo.co.uk: -- stage: - patch review versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6689 ___

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

Stefan Krah stefan-use...@bytereef.org added the comment: This is a request for changing the current behavior on Unix, and I doubt this is going to happen, since it could break existing code. On a side note, there are already two ways get the desired output: Popen(gcc --version, shell=True)

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

Berwyn ber...@brush.co.nz added the comment: I think this should be documented more clearly rather than just rejected. It keeps causing various people grief. David Fraser's post would be good documentation. -- status: pending - open ___ Python

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

Stefan Krah stefan-use...@bytereef.org added the comment: I find this particular section one of the most clear sections in the whole Python documentation: On Unix, with shell=True: If args is a string, it specifies the command string to execute through the shell. This means that the string

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

Berwyn ber...@brush.co.nz added the comment: Good point, Stefan. In hindsight my issue was probably more with understanding how the sh command line works rather than how python works. -- status: pending - open ___ Python tracker

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

Stefan Krah stefan-use...@bytereef.org added the comment: I'm glad you agree. Closing this now. -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6689 ___

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

R. David Murray rdmur...@bitdance.com added the comment: Note that the clear wording was only introduced on 2/4 of this year (issue 6770). -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6689

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

Changes by R. David Murray rdmur...@bitdance.com: -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6689 ___ ___ Python-bugs-list mailing list

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

Berwyn ber...@brush.co.nz added the comment: Ah. I don't need to feel so forgetful, then. -- title: subprocess doesn't pass arguments correctly on Linux when shell=True - subprocess doesn't pass arguments correctly on Linux whenshell=True

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

David Fraser dav...@sjsoft.com added the comment: Ah, upon closer inspection - the special parameters $0 $1 $2 etc mentioned in the sh docs refer to parameters within the command string, so that: sh -c 'echo $2 $0 $1' run for the people produces: the people run for So the correct patch

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

Changes by David Fraser dav...@sjsoft.com: Removed file: http://bugs.python.org/file14697/current-2.6.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6689 ___

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

Changes by David Fraser dav...@sjsoft.com: Removed file: http://bugs.python.org/file14698/current-3.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6689 ___

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

New submission from David Fraser dav...@sjsoft.com: (from http://stackoverflow.com/questions/1253122/why-does-subprocess-popen-with-shelltrue-work-differently-on-linux-vs-windows/1254322) When using subprocess.Popen(args, shell=True) to run gcc --version (just as an example), on Windows we get

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

Changes by David Fraser dav...@sjsoft.com: Added file: http://bugs.python.org/file14698/current-3.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6689 ___

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

Changes by Ben Hoyt benh...@gmail.com: -- nosy: +benhoyt type: behavior - feature request ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6689 ___

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

Ben Hoyt benh...@gmail.com added the comment: Oops, didn't intend to change the type, changing back. -- type: feature request - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6689

[issue6689] subprocess doesn't pass arguments correctly on Linux when shell=True

Berwyn ber...@brush.co.nz added the comment: I agree with the patch, and it works fine: /bin/sh -c gcc --version gcc --version But I begin to wonder whether bash has a bug since bash only seems to observe the string, not the parameters after it. For example: $ bash -c ./printargs.py