From 9d9f18db05e872e93685473314cc72af6a65960c Mon Sep 17 00:00:00 2001 From: Sean Stoube <31805425+HoneyBearTech@users.noreply.github.com> Date: Wed, 18 Nov 2026 15:38:37 -0600 Subject: [PATCH] docs: clarify that global context names are not import paths (#729) The global context table lists names like modules.MODULE, which reads as if a module could be imported that way. Say that these names are only used for logging, reloads and the global context functions, and that a module is imported with "import MODULE". Signed-off-by: Sean Stoube <31805425+HoneyBearTech@users.noreply.github.com> --- docs/reference.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/reference.rst b/docs/reference.rst index 1d7ef75..d649c9b 100644 --- a/docs/reference.rst +++ b/docs/reference.rst @@ -1684,6 +1684,11 @@ lower case means actual fixed names): ``pyscript/scripts/DIR1/DIR2/FILE.py`` ``scripts.DIR1.DIR2.FILE`` ======================================= =========================== +These are internal names for each global context, used in logging paths, reloads and the global +context functions below; they are not import paths. For example, a module in +``pyscript/modules/MODULE.py`` is imported with ``import MODULE``, not ``import modules.MODULE`` +(see `Importing`_). + Note that if the package form of an app or module (``pyscript/apps/APP/__init__.py`` or ``pyscript/modules/MODULE/__init__.py``) exists, the module form (``pyscript/apps/APP.py`` or ``pyscript/modules/MODULE.py``) is ignored.