Clarify `inherit_parent_main` docstring scope
Note the opt-out only applies to the trio spawn backend; `multiprocessing` `spawn`/`forkserver` reconstruct `__main__` via stdlib bootstrap. Review: PR #438 (Copilot) https://github.com/goodboy/tractor/pull/438 (this patch was generated in some part by [`claude-code`][claude-code-gh]) [claude-code-gh]: https://github.com/anthropics/claude-codesubint_spawner_backend
parent
c6c591e61a
commit
acf6568275
|
|
@ -207,9 +207,12 @@ class ActorNursery:
|
|||
Start a (daemon) actor: an process that has no designated
|
||||
"main task" besides the runtime.
|
||||
|
||||
Pass ``inherit_parent_main=False`` to keep this child on its own
|
||||
bootstrap module instead of re-running the parent's ``__main__``
|
||||
during startup.
|
||||
Pass ``inherit_parent_main=False`` to keep this child on its
|
||||
own bootstrap module for the trio spawn backend instead of
|
||||
applying the parent ``__main__`` re-exec fixup during startup.
|
||||
This does not affect ``multiprocessing`` ``spawn`` or
|
||||
``forkserver`` which reconstruct the parent's ``__main__`` as
|
||||
part of their normal stdlib bootstrap.
|
||||
|
||||
'''
|
||||
__runtimeframe__: int = 1 # noqa
|
||||
|
|
|
|||
Loading…
Reference in New Issue