[issue45048] subprocess.run(capture_output=Bool) does the opposite of expected

DragonEggBedrockBreaking added the comment: Ok, thanks, I understand now. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___

[issue45048] subprocess.run(capture_output=Bool) does the opposite of expected

Eryk Sun added the comment: The documentation states that "[i]f capture_output is true, stdout and stderr will be captured". This implies a container of some kind. So look to what subprocess.run() returns: "[w]ait for command to complete, then return a CompletedProcess instance". The

[issue45048] subprocess.run(capture_output=Bool) does the opposite of expected

DragonEggBedrockBreaking added the comment: I read the documentation, and I saw in the example that when capture_output was true, command output was printed, otherwise it isn't printed. my observations directly contradict the examples given in the docs, as stated in my original issue.

[issue45048] subprocess.run(capture_output=Bool) does the opposite of expected

Vedran Čačić added the comment: I think it is exactly what "capture" means: "not allow it to escape" (to the console). Maybe you should read the documentation? -- nosy: +veky ___ Python tracker

[issue45048] subprocess.run(capture_output=Bool) does the opposite of expected

New submission from DragonEggBedrockBreaking : If you run subprocess.run(capture_output=True), it doesn't show output, but if you run subprocess.run(capture_output=False) (or if you just run subprocess.run() since False is default), it does show output. In the example in the docs, it shows