On 1/9/23, c.bu...@posteo.jp wrote:
>
> On Python for Windows what is the appropriate way how a process can call
> itself again?
>
> Let me give you an example [1]:
> There is a project "bitcli" having two entry points
>
> [project.scripts]
> bitcli = "bitcli.__main__:main"
> bitcli-root =
Dear Eryk,
Am 08.01.2023 17:22 schrieb Eryk Sun:
Avoid using any of the `os.exec*` functions on Windows. There's no
support for replacing a Windows process image, so the `exec*()`
functions simply spawn a child process and terminate the current one.
Thanks for bringing this up.
On Python for
On 1/8/23, c.bu...@posteo.jp wrote:
>
> is there an equivalent in the subprocess module for "os.execvp()" to
> replace the current process with the new called one?
A note for Windows users
Avoid using any of the `os.exec*` functions on Windows. There's no
support for replacing a Windows process
On Sun, 8 Jan 2023 at 21:51, wrote:
>
> Hello,
>
> is there an equivalent in the subprocess module for "os.execvp()" to
> replace the current process with the new called one?
It won't make a subprocess, so no. It's in the os module - under the
name execvp. You found it already :)
ChrisA
--
Hello,
is there an equivalent in the subprocess module for "os.execvp()" to
replace the current process with the new called one?
Kind
Christian
--
https://mail.python.org/mailman/listinfo/python-list
