[issue40467] subprocess: replacement shell on windows with executable="..." arg

Change by Eryk Sun : -- versions: +Python 3.10, Python 3.11 -Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue40467] subprocess: replacement shell on windows with executable="..." arg

Eryk Sun added the comment: > it might be nice if it's possible to give some sort of useful > warning/error when this happens -- perhaps say that specifying > both shell=True and executable="..." isn't supported on Windows? The `shell` parameter is documented as follows for Windows: On

[issue40467] subprocess: replacement shell on windows with executable="..." arg

Joe Cool added the comment: Proposed solution: if comspec.endswith('sh.exe') or comspec.endswith('sh'):# issue 40467 args = '{} -c "{}"'.format (comspec, args) # issue 40467 else:

[issue40467] subprocess: replacement shell on windows with executable="..." arg

New submission from Anish Athalye : On Windows, using subprocess.call() and specifying both shell=True and the executable='...' keyword arguments produces an undesirable result when the specified shell is a POSIX-like shell rather than the standard cmd.exe. I think the documentation is unclear