Skip to content

Add a linter-only Python type item to the backlog - #431

Merged
ptr727 merged 1 commit into
developfrom
linter-only-python-type-todo
Jul 25, 2026
Merged

Add a linter-only Python type item to the backlog#431
ptr727 merged 1 commit into
developfrom
linter-only-python-type-todo

Conversation

@ptr727

@ptr727 ptr727 commented Jul 25, 2026

Copy link
Copy Markdown
Owner

Adds one backlog item: a linter-only Python project type for codegen/boilerplate Python (no tests, no coverage, linter only) distinct from the existing python type for utility code (tests + coverage). Records that ESPHome-Config's +python reclassification is deferred until the type exists, and its one outstanding finding is accepted meanwhile.

Docs-only. spec/validate.py OK.

🤖 Generated with Claude Code

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 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 25, 2026 00:55

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the repository TODO backlog to track adding a new "linter-only" Python project type intended for codegen/boilerplate Python (linting only, no unit tests/coverage), distinct from the existing python type meant for utility code that should carry tests and coverage.

Changes:

  • Add a backlog item to introduce a linter-only Python project type for build-time code generation/boilerplate Python.
  • Record that ESPHome-Config stays source-only for now and its deferred +python reclassification is contingent on this new type, with its current validation finding accepted meanwhile.

@ptr727
ptr727 merged commit e12f38e into develop Jul 25, 2026
7 checks passed
@ptr727
ptr727 deleted the linter-only-python-type-todo branch July 25, 2026 00:59
ptr727 added a commit that referenced this pull request Jul 25, 2026
…) (#434)

## Promote develop to main

Four doc/spec-only changes, all squashed to develop and Copilot-clean:

- **#430** - README backlog: refresh the stale README + evaluate a
lower-maintenance structure.
- **#431** - README backlog: a linter-only Python type
(codegen/boilerplate: no tests/coverage, linter only) distinct from the
utility `python` type; ESPHome-Config `+python` deferred until it
exists.
- **#432** - `audit.py` branch check now splits "develop genuinely
behind" (forward-sync) from "changed on both / develop may supersede",
with a `classify_branch_drift()` helper + selftest. Surfaced by the
PlexCleaner convergence, where develop was ahead but read as a
forward-sync gap.
- **#433** - canonical `build-release-task.yml` artifact-delete uses the
`if ! …; then` form instead of a force-success tail (matches the listing
step; write-safety compliant). Changes the `github-release` verbatim
region → fleet re-vendors next cycle.

No code/workflow changes to the hub's own pipeline - documentation and
spec only, so no release fires on merge.

## Verification

- `spec/validate.py` OK; `spec/audit.py --selftest` PASS.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants