v1.4.1: Setup Keeps a Working venv

🐛 Fixes

PyPilot 1.4.1 fixes how pypilot setup treats an existing environment on Windows.

• Setup keeps a venv that is already right. If .venv already runs the Python setup chooses, still has its interpreter and does not pull in the base Python's packages, setup keeps it and only syncs the packages. Before, it always rebuilt the venv.
• A venv in use is never half-deleted. Rebuilding a venv while the editor runs its Python (a language server, a notebook kernel, an activated terminal) failed with Access is denied. (os error 5) on .venv\Scripts, but only after uv had already deleted every installed package. Now setup, doctor --fix and install check first, leave the venv untouched, and say what to close: python.exe in .venv is running, so PyPilot left the environment as it is.

🧭 Zed tasks

• The task templates are now tasks/windows.json and tasks/macos-linux.json. They run the pypilot on your PATH, or else the copy the Zed extension downloaded, so they work on a machine where only the extension is installed. Copy the one for your OS again to get this.

The Zed extension picks up this engine the next time Zed starts. The VS Code extension and pypilot-cli still ship 1.4.0.

---

📦 Installation

Via Zed (recommended): Install the PyPilot extension from the Zed extension registry

Verify a download:

sha256sum -c SHA256SUMS --ignore-missing
gh attestation verify pypilot-linux-x64.tar.gz -R pypilot-dev/pypilot

Full Changelog: v1.4.0...v1.4.1