Detect WHICH Python launches a REPL or a run_tests shell-out, mirroring how
the Clojure pack picks deps.edn / lein / bb. The project-managed environment
is detected so the interpreter sees the project's dependencies.
Detect WHICH Python launches a REPL or a `run_tests` shell-out, mirroring how the Clojure pack picks deps.edn / lein / bb. The project-managed environment is detected so the interpreter sees the project's dependencies.
(configured-runner)python.runner from merged config, or nil. Config failures degrade to nil
rather than breaking a run.
`python.runner` from merged config, or nil. Config failures degrade to nil rather than breaking a run.
(detect-command root)The argv PREFIX that launches a project-aware Python in root.
Detection order (first hit wins):
uv on PATH → [uv run python]poetry on PATH → [poetry run python]The argv PREFIX that launches a project-aware Python in `root`. Detection order (first hit wins): 1. uv — uv.lock / [tool.uv] in pyproject + `uv` on PATH → [uv run python] 2. poetry — poetry.lock + `poetry` on PATH → [poetry run python] 3. venv — .venv/ or venv/ interpreter → [<abs path>] 4. system — python3, else python → [python3]
(pinned-runner raw-config)The run_tests backend raw-config pins as python.runner (vispython or
project), or nil for anything else. Explicit call arguments still win.
The `run_tests` backend `raw-config` pins as `python.runner` (`vispython` or `project`), or nil for anything else. Explicit call arguments still win.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |