From ce38cb6f0ea709f9c6644c220d7168f4bc6723d8 Mon Sep 17 00:00:00 2001 From: goodboy Date: Fri, 21 Aug 2026 01:52:24 -0400 Subject: [PATCH] Correct `to_actor.run()` target guidance Target validation moved to a follow-up branch, so the guide should not claim unstable callable forms are rejected before actor startup. Describe module-global functions and `functools.partial()` wrappers as portable stable-address forms without promising absent enforcement. (this patch was generated in some part by `opencode` using `gpt-5.6-sol` (`openai`)) --- docs/guide/spawning.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/guide/spawning.rst b/docs/guide/spawning.rst index 28842bf6..a63e75f6 100644 --- a/docs/guide/spawning.rst +++ b/docs/guide/spawning.rst @@ -126,10 +126,10 @@ A few details worth knowing: ``name='something_cuter'``. - the function's module is auto-added to the child's ``enable_modules`` allowlist. -- the target must be a module-global async function, or a - ``functools.partial`` thereof. Nested functions, methods and callable - objects have no stable ``module:name`` RPC address and are rejected - before actor startup. +- targets cross IPC as ``module:name`` references, so portable calls + use module-global async functions or ``functools.partial`` objects + wrapping them. Nested functions, methods and callable objects do not + provide that stable address. - target arguments are positional; use ``functools.partial()`` to bind target keyword arguments. Keywords passed directly to ``run()`` configure actor placement and spawning.