What the developer wrote
Authored by odudex
fix: add src to poe task PYTHONPATH
Ensure poe-launched commands can import the local krux package under uv, where the project itself is not installed as a package.
What changed, and why it matters
This commit adjusts how a Python build tool (poe) finds the project's own source code when running commands. It adds the local 'src' directory to the PYTHONPATH environment variable for poe tasks. There is no indication this is a security fix; it is a development workflow fix to make local imports work correctly under the 'uv' packaging tool.
No security action required. Treat as a normal build/tooling fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change adds a [tool.poe.env] section in pyproject.toml setting PYTHONPATH to include ${POE_ROOT}/src. This ensures poe-launched tasks can import the local krux package when the project is not installed as an editable package under uv. The diff only touches pyproject.toml and adds three lines. No runtime code, cryptographic logic, firmware, or user-facing behavior is changed.
Changed components
pyproject.tomlpoe task environment configurationInspect captured patch +3 / −0
diff --git a/pyproject.toml b/pyproject.toml
index bd4cfa6..38e02ef 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -82,6 +82,9 @@ urtypes = { path = "vendor/urtypes", editable = true }
[tool.pytest.ini_options]
pythonpath = ["src"]
+[tool.poe.env]
+PYTHONPATH = "${POE_ROOT}/src${PYTHONPATH:+:${PYTHONPATH}}"
+
[tool.poe.tasks]
# format tasks
format-src = "black src"
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.