Add pyproject.toml and proper Python packaging #4

New issue

Closed

opened 2026-05-14 04:47:39 +00:00 by Mark · 0 comments

Mark commented

2026-05-14 04:47:39 +00:00

Owner

The testenv/ package is currently copied manually into /opt/testenv/lib/python3.12/site-packages/ in the Dockerfile. This is fragile and non-standard.

Add:

pyproject.toml with [build-system] (setuptools or hatchling)
[project] metadata (name, version, description, dependencies)
[project.optional-dependencies] for test (pytest, pytest-html, pytest-xvfb)
[project.scripts] for CLI entry points (testenv-shell, deploy-app)
Update Dockerfile to pip install . instead of manual COPY

Why: Standard packaging enables pip install, version pinning, dependency resolution, and publishing to a private package index.

The `testenv/` package is currently copied manually into `/opt/testenv/lib/python3.12/site-packages/` in the Dockerfile. This is fragile and non-standard. Add: - `pyproject.toml` with `[build-system]` (setuptools or hatchling) - `[project]` metadata (name, version, description, dependencies) - `[project.optional-dependencies]` for `test` (pytest, pytest-html, pytest-xvfb) - `[project.scripts]` for CLI entry points (`testenv-shell`, `deploy-app`) - Update `Dockerfile` to `pip install .` instead of manual COPY **Why:** Standard packaging enables `pip install`, version pinning, dependency resolution, and publishing to a private package index.