@@ -4794,16 +4794,16 @@ written in Python, such as a mail server's external command delivery program.
47944794 .. versionadded :: 3.7
47954795
47964796
4797- .. function :: spawnl(mode, path , ...)
4798- spawnle(mode, path , ..., env)
4797+ .. function :: spawnl(mode, file , ...)
4798+ spawnle(mode, file , ..., env)
47994799 spawnlp(mode, file, ...)
48004800 spawnlpe(mode, file, ..., env)
4801- spawnv(mode, path , args)
4802- spawnve(mode, path , args, env)
4801+ spawnv(mode, file , args)
4802+ spawnve(mode, file , args, env)
48034803 spawnvp(mode, file, args)
48044804 spawnvpe(mode, file, args, env)
48054805
4806- Execute the program *path * in a new process.
4806+ Execute the program *file * in a new process.
48074807
48084808 (Note that the :mod: `subprocess ` module provides more powerful facilities for
48094809 spawning new processes and retrieving their results; using that module is
@@ -4835,7 +4835,7 @@ written in Python, such as a mail server's external command delivery program.
48354835 discussed in the next paragraph), the new environment is used as the source of
48364836 the :envvar: `PATH ` variable. The other variants, :func: `spawnl `,
48374837 :func: `spawnle `, :func: `spawnv `, and :func: `spawnve `, will not use the
4838- :envvar: `PATH ` variable to locate the executable; *path * must contain an
4838+ :envvar: `PATH ` variable to locate the executable; *file * must contain an
48394839 appropriate absolute or relative path.
48404840
48414841 For :func: `spawnle `, :func: `spawnlpe `, :func: `spawnve `, and :func: `spawnvpe `
0 commit comments