[issue22712] Add 'input' argument to subprocess.check_call and subprocess.call

Serhiy Storchaka added the comment: Then I'm closing this issue. -- resolution: -> rejected stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue22712] Add 'input' argument to subprocess.check_call and subprocess.call

zodalahtathi added the comment: I think the 'stdin argument can be any file like or stream for all subprocess functions' approach would be the best solution, because it is misleading to differentiate behavior based on internal implementation details (the use of communicate), when the function

[issue22712] Add 'input' argument to subprocess.check_call and subprocess.call

R. David Murray added the comment: call and check_call are designed as APIs that do *not* manage the standard streams of the commands called. If you want to manage the streams, either use check_output or Popen directly. Internally, call and check call do *not* use communicate, and it is commu

[issue22712] Add 'input' argument to subprocess.check_call and subprocess.call

New submission from zodalahtathi: Python 3.4 added a 'input' argument to the subprocess.check_output function to send bytes to stdin, but it was surprisingly not added to other subprocess helpers. The same functionality should be added to subprocess.check_call and subprocess.call. --