From d6cb01987c351d0dee734c7ff9ff4a5c0799aa2e Mon Sep 17 00:00:00 2001 From: Godopu Date: Thu, 8 Oct 2026 08:12:44 +0900 Subject: [PATCH] docs(issue-17): wrapper.py imports only the stdlib, the package it runs in loads paho (N1) "Stdlib only" is true of the module, not of how the wrapper runs it: `python -m lib_py.delegation.wrapper` imports lib_py/delegation/__init__.py first, which loads the service and paho-mqtt. The docstring now says so; the wrapper's $PY already needs paho. The run path is unchanged. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01HCGpJXhSZasJLU38ksDghe --- .agents/skills/lib_py/delegation/wrapper.py | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/.agents/skills/lib_py/delegation/wrapper.py b/.agents/skills/lib_py/delegation/wrapper.py index 4f5a589..8a8e10e 100644 --- a/.agents/skills/lib_py/delegation/wrapper.py +++ b/.agents/skills/lib_py/delegation/wrapper.py @@ -21,8 +21,12 @@ checks that the wrapper is still alive throughout both waits and before each side effect, and leaves without closing or publishing once it is gone - as the same loops in bash ended with the wrapper. -Stdlib only and Python 3.9 (macOS /usr/bin/python3); registry.py and -publish_event.py run as the processes the wrapper ran, with its interpreter. +This module imports only the standard library and runs on Python 3.9 (macOS +/usr/bin/python3). The wrapper runs it as `python -m lib_py.delegation.wrapper`, +which imports the package first: lib_py/delegation/__init__.py loads the +service and with it paho-mqtt, so the wrapper's $PY needs paho - as it always +did for the subscriber and publish_event.py. registry.py and publish_event.py +run as the processes the wrapper ran, with its interpreter. """ from __future__ import annotations