If the child process has an orderly termination sequence (such as sending Would make it tricky to cleanly terminate the child process when we're done with Interact with it (via a known port, for example) in another thread. Sure, we could launch a child process with n in one thread and
We'll have to look at some of the lower-level APIs.
This would be difficult toĪchieve with APIs that just run a child process to completion synchronously, so Shut down the child process in an orderly way. We launch it as a child process, thenĬonnect clients to it and run some testing sequence. In this post I want to discuss a variation of this task that is lessĭirectly addressed - long-running child processes.
It comes with several high-level APIs likeĬall, check_output and (starting with Python 3.5) run that areįocused at child processes our program runs and waits to complete. If starting a separate thread make sure the thread doesn’t share resources with the skill object since this will hinder garbage collection when the skill is reloaded.The Python subprocess module is a powerful swiss-army knife for launchingĪnd interacting with child processes. You can start a process and detatch it once and then check if the process is running (either communication or search for running processes) If the process don’t need to outlive the skill I recommend starting the process in the _init_() method and having a custom shutdown method (override shutdown()) that terminates the subprocess in a neat way (I don’t always practice what I preach) I assume you want the process to outlive the skill start/shutdown?įor ease of installation an already running daemon is most likely not practical, since the normal skill install method doesn’t accommodate for installing custom services. There are however bad and good ways of doing this This is a great topic that may need some discussion as there are no firm rules or regulations ( anything goes).
0 kommentar(er)
