KopfRunner enters the operator through the CLI, requiring module paths and Click invocation. The new runners enter via operator() directly, making them suitable for programmatic tests where the handlers are already registered in the process: KopfThread as a sync context manager running in a background thread, and KopfTask as an async context manager running as a background asyncio task. Both inject a stop flag if not provided, set it on context exit for graceful shutdown, and support timeout and reraise semantics matching KopfRunner.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Signed-off-by: Sergey Vasilyev <[email protected]>

…nner

Signed-off-by: Sergey Vasilyev <[email protected]>

The Flag type union and the wait_flag/raise_flag/check_flag match blocks only handled in-process primitives (asyncio, threading, concurrent.futures). The upcoming KopfCLI subprocess runner needs to pass a `multiprocessing.Event` across process boundaries as a stop flag. This extends all three functions with a dedicated `multiprocessing.synchronize.Event` arm — kept separate from `threading.Event` despite the identical API, since they are semantically distinct (in-process vs cross-process).

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Signed-off-by: Sergey Vasilyev <[email protected]>

…lation

KopfRunner uses Click's CliRunner in a thread, which shares sys.modules with the parent process. This breaks module-based loading (`kopf run -m mymodule`) because importlib.import_module() is a no-op for already-imported modules — decorators don't re-execute, the isolated registry stays empty, and the operator runs with no handlers.

KopfCLI spawns the operator in a child process via multiprocessing with the 'spawn' start method, giving it a fresh Python interpreter where imports execute from scratch. It supports two shutdown modes: a cross-process stop flag (default, clean exit) and signal-based shutdown (SIGTERM/SIGINT, testing the production shutdown path). Output is captured via an os-level pipe with a background reader thread, readable both during the run and after exit.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
Signed-off-by: Sergey Vasilyev <[email protected]>

KopfRunner runs the CLI in a thread sharing sys.modules with the parent, which breaks module-based loading due to lack of import isolation. Emit a DeprecationWarning pointing users to the appropriate replacements and the documentation.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Signed-off-by: Sergey Vasilyev <[email protected]>

Signed-off-by: Sergey Vasilyev <[email protected]>