Files
pipdock/.gitignore
T
poli0981andClaude Opus 5 c281d054c0 fix(core): pip upkeep runs pip, whatever engine is configured
`pipdock pip-upgrade --engine uv` failed at PD-ENG-001 — while the line immediately below
had already reached past the abstraction to call PipEngine.info directly for the version.

Upgrading pip is a pip operation by definition. There is no uv way to do it, which is why
UvEngine::upgrade_pip exists only to refuse, and the engine setting is a preference about
the *user's* environments. Dispatching on it meant the one command with no resolver
between the user and the result was also the one that could be blocked by an unrelated
choice. Same reasoning P2 applied to the tools venv: pip is present wherever Python is.

Both heads now call PipEngine::upgrade_pip directly. The uv refusal stays rather than
becoming an unreachable!() — the trait is public and for_id can still hand a caller that
adapter, where a catalog code beats a panic.

That refusal was also the only thing standing in front of this path, so PipEngine now
carries its own PEP 668 guard, copied verbatim from UninstallFlow::start rather than
reworded so the three cannot drift. DATA-FLOW §2's preamble is "all mutating flows" and
replacing pip in site-packages is one; UpdateFlow has refused since S1 and UninstallFlow
since S5, and this had no guard at all. It stayed harmless only while nothing but a CLI
command could reach it — the next commit gives it a button.

Verified by running: `pip-upgrade --engine uv` on a 3.12 venv reports pip 25.0.1 -> 26.2.1
and exits 0, and a second run is idempotent.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-12 22:45:02 +07:00

56 lines
1.1 KiB
Plaintext

# Rust
/target/
/src-tauri/target/
**/*.rs.bk
# Node
node_modules/
dist/
dist-ssr/
.vite/
*.tsbuildinfo
# Tauri build output
/src-tauri/gen/
# Environments (test venvs created by the integration suite / spikes)
.venv/
venv/
# Verifying an environment feature by hand needs a venv the GUI can *see*, and `env_add_manual`
# (Browse…) is still owed — so venv_scan's "below the working directory" is the only way in, which
# means the repo root. `.venv-oldpip` for the pip-upkeep floor, and whatever the next one needs.
/.venv-*/
__pycache__/
*.py[cod]
# ci-integration.yml builds these in the workspace. Harmless on an ephemeral runner, but a
# developer running the same steps locally gets an untracked venv that `git add -A` would sweep up.
/.itest/
/.uvtools/
/.itest-appdata/
# Editors / IDEs
.idea/
.vs/
.vscode/*
!.vscode/extensions.json
*.swp
# OS
Thumbs.db
Desktop.ini
.DS_Store
# Secrets & local config
.env
.env.*
!.env.example
*.key
tauri-signing-private.key*
# Logs & scratch
*.log
/spikes/out/
# Spike tooling venvs (SP-1 needs several uv versions side by side)
/spikes/.venv*/