homelab/stack
1
0
Fork 0
Code Issues 70 Pull Requests 1 Actions Packages Projects 1 Releases Wiki Activity

Align Python version pins: .python-version vs CI vs pyproject.toml #59

New Issue
Closed
opened 2026-03-21 19:12:14 +00:00 by kert · 0 comments
kert commented 2026-03-21 19:12:14 +00:00
Owner
Copy Link

Problem

Three different Python version specs:

Source Version Note
.python-version cpython-3.13.12-linux-x86_64-gnu Exact platform-specific pin
pyproject.toml >=3.12 Loose floor
.woodpecker/ci.yml line 16 uv python pin 3.13.11 Downgrades to 3.13.11!

The CI step actively fights the .python-version pin. This can cause version skew between local and CI.

Fix

  1. Pick ONE version: 3.13 (minor pin, let patch float)
  2. Set .python-version to 3.13 (uv will resolve latest patch)
  3. Remove uv python pin 3.13.11 from CI — let it respect .python-version
  4. Keep requires-python = ">=3.12" in pyproject.toml (library compat floor)

Files

  • .python-version
  • .woodpecker/ci.yml
## Problem Three different Python version specs: | Source | Version | Note | |--------|---------|------| | `.python-version` | `cpython-3.13.12-linux-x86_64-gnu` | Exact platform-specific pin | | `pyproject.toml` | `>=3.12` | Loose floor | | `.woodpecker/ci.yml` line 16 | `uv python pin 3.13.11` | **Downgrades** to 3.13.11! | The CI step actively fights the `.python-version` pin. This can cause version skew between local and CI. ## Fix 1. Pick ONE version: `3.13` (minor pin, let patch float) 2. Set `.python-version` to `3.13` (uv will resolve latest patch) 3. Remove `uv python pin 3.13.11` from CI — let it respect `.python-version` 4. Keep `requires-python = ">=3.12"` in pyproject.toml (library compat floor) ## Files - `.python-version` - `.woodpecker/ci.yml`
kert added this to the P12: uv Hygiene — fix venv, build system, python resolution milestone 2026-03-21 19:12:14 +00:00
kert added the config label 2026-03-21 19:12:14 +00:00
kert closed this issue 2026-03-21 19:34:02 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
REST API (FastAPI)
 auth
Authentication and authorization
 bib
Bibliography, Zotero, citations
 ci
CI/CD pipelines and Woodpecker plugins
 cli
CLI commands and UX
 cloud
Cloud provider abstraction (AWS, GCP, Azure, self-hosted)
 config
Configuration and wiring
 data
Data loading, CCLF, BCDA, seeds
 databricks
Databricks jobs and deployment
 docs
Documentation and generated references
 image:api
image:docs
image:mc
image:notebooks
image:zotero
infra
lakehouse
Nessie, Polaris, Trino, Iceberg
 llm
llm module — local RAG over comments + Zotero corpus
 notebooks
marimo notebook errors (auto-filed by nb-watcher/nb-integration)
 packaging
Python packaging, optional deps, build system
 pfs
pipeline
Pipeline execution and validation
 pipeline:ci
pipeline:deploy
pipeline:harden
pipeline:infra-ci
pipeline:rebuild-all
pipeline:release
qpp
quality
Testing, coverage, error handling
 step:build
step:deploy
step:hadolint
step:lint
step:publish
step:scan
step:test
step:validate
styles
Charts, figures, visual theming
 tree
Project directory structure and file organization
No Label config
Milestone
No items
No Milestone P12: uv Hygiene — fix venv, build system, python resolution
Projects
Clear projects
No project
Assignees
Clear assignees
kert renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: homelab/stack#59
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?