Python subprocess.run Command: Capture Output Safely

Select a timestamp to watch that moment on YouTube.

1. 00:00

   subprocess.run launches a child process on your local machine and waits for it. Pass a sequence of program and argument strings rather than one shell command string. In this tutorial the executable is sys.executable, which selects the same Python interpreter as the parent. Use capture_output=True and text=True when you want stdout and stderr as decoded strings. The first code sample is for a normal local Python interpreter. sys.executable identifies the interpreter already running the parent, and the list gives it -c and a fixed code string as separate arguments. subprocess.run waits for the child.

2. 00:40

   capture_output=True stores stdout and stderr; text=True decodes them into strings; timeout=5 bounds the wait. Notice what capture_output does not do: it does not decide whether the child succeeded. A process can write a helpful message to stdout and still exit nonzero, or write a warning to stderr and still exit zero. Read returncode or request check=True based on the caller's policy. Do not infer success solely from nonempty text. The second local run makes this visible by printing a diagnostic and exiting with three. Check the CompletedProcess.returncode, or use check=True to raise CalledProcessError

3. 01:23

   for a nonzero exit. Set a timeout so a stuck child cannot block forever. The video demonstrates an actual local Python child that prints a greeting, then a failing child whose stderr is captured. A string such as 'python -c ...' with the default shell=False is not automatically split into a program and its arguments. The browser exercise cannot launch an operating-system child. It builds the same argv shape but leaves execution to a local script. Do not interpret a browser failure to run subprocess as a defect in the command builder. Copy the sample into a local Python 3 process to observe the child return code

4. 02:06

   and greeting. The second local child writes bad to stderr and exits with status 3. With check=False, the default, subprocess.run still returns a CompletedProcess: its returncode is 3 and its stderr contains the message. If you set check=True, the call instead raises CalledProcessError for that nonzero status. Keep user input as a separate argument, not part of the code string or a shell command. The child receives it through sys.argv. shell=True changes the security model and is unnecessary for this known Python command.

5. 02:46

   Production callers should also decide which working directory and environment the child may inherit, and should avoid printing secrets from captured streams. A useful caller must choose an error policy rather than merely print captured text. Preserve stderr for diagnostics, avoid showing sensitive environment details to end users, and set timeout for potentially stalled children. For a trusted Python child, no shell is needed. A browser-based Python runtime cannot launch operating-system child processes. The interactive task here therefore builds and validates an argv list but never claims to run it.

6. 03:26

   Copy the local example into a normal Python 3 environment to see subprocess.run in action. This page complements the site's CLI exit- code and shlex lessons: one teaches how programs report status; this one teaches a caller how to launch and inspect a known child. The browser-safe example only constructs argv and prints its length and final item. Punctuation in the name stays in that one data argument. A shell would interpret some punctuation as syntax, so avoid concatenating untrusted text into a command string or enabling shell=True without a concrete reason.

7. 04:06

   The checked task rejects blank names and returns a four-element list. It never calls subprocess in the browser. In local code, use that list with subprocess.run and consider a fixed cwd and narrowly selected environment if the child should not inherit all of the parent process's context. The lesson is about a known program, not running arbitrary commands supplied by a visitor. Return an argument list [sys.executable, '-c', fixed_code, name] from greeting_command(name), where fixed_code prints Hello, followed by sys.argv[1]. Reject a blank name with ValueError. This browser task only builds argv; run subprocess.run with the list in local

8. 04:48

   Python as shown in the guide. We use the same Python interpreter as the parent so the demonstration does not depend on a python command being installed on PATH. If you instead launch a project tool, use a known executable path and keep its arguments separate. A timeout limits how long run waits after the child starts, but process startup itself may still take time. Handling TimeoutExpired and choosing whether to retry are operational decisions for a larger application. The example deliberately does not execute arbitrary visitor input. The only dynamic value is the name passed as one argument.

9. 05:31

   This distinction is essential: shell punctuation inside that name remains data when no shell is invoked. If a workflow truly needs a shell pipeline, review the shell's quoting and trust boundary separately. For this greeting child, shell=True would add complexity and risk without adding value. At PythonLessonLab, work through the matching lesson and run the checked task. Explain the output before changing the code, then make one small change and rerun the boundary case. The result matters more than memorizing a function name: you should know what it accepts, what it returns, and which failure it prevents.