From fd3a4c017c0c2af8b529592f68a76786102c787c Mon Sep 17 00:00:00 2001 From: Pieter Viljoen Date: Fri, 24 Jul 2026 17:55:48 -0700 Subject: [PATCH] Add a linter-only Python type item to the backlog Two kinds of Python need different project-type requirements: utility code (as in PlexCleaner) can and should carry unit tests and coverage, while codegen/boilerplate that runs during another tool's build to emit generated source (ESPHome codegen producing enriched C++) has no tests and no coverage and needs only the linter. Capture the work to add a linter-only Python type, and record that ESPHome-Config's +python reclassification is deferred until it exists. Co-Authored-By: Claude Opus 4.8 --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 56906e8b..827abfe8 100644 --- a/README.md +++ b/README.md @@ -139,6 +139,7 @@ Running backlog (kept here, in a committed file, so the guidance survives across - Sweep `ManagePackageVersionsCentrally` placement to `Directory.Packages.props` fleet-wide (PlexCleaner sets it in `Directory.Build.props`, off the CODESTYLE canonical). - Finish onboarding hardening (from #310): make the `AUDIT.md` audit a required onboarding step and run the per-type cold-start self-tests tracked in `reports/conformance-matrix.md` (`STANDUP.md` is already in place). - Refresh the README (it has gone stale) and evaluate a lower-maintenance structure - for example a per-section index that points into each doc with a one-line description, keeping the README as the adoption and audit-instruction entry point with pointers to the other docs. A per-section index trades brevity for a sync obligation: it must track what the docs contain. +- Add a linter-only Python project type for codegen/boilerplate Python - code that runs during another tool's build to emit generated source (e.g. ESPHome codegen that produces enriched C++ at compile time), so it ships no unit tests and no coverage and needs only the linter. Keep it distinct from the existing `python` type, which is utility code that can and should carry unit tests and coverage (as in PlexCleaner). Until it exists, ESPHome-Config stays `source-only` and its `+python` reclassification is deferred - accept its one outstanding validation finding meanwhile. ## License