🐛 fix(venv): seed pip into hook environments by gaborbernat · Pull Request #114 · tox-dev/pre-commit-uv

gaborbernat · 2026-02-18T04:49:13Z

uv venv does not install pip into virtual environments by default, unlike python -m venv. Hooks such as mypy that internally call python -m pip install at runtime (e.g. to fetch missing type stubs) fail with No module named pip in the hook environment. This affects CI environments where pre-commit-uv manages hook installation.

Passing --seed to uv venv restores pip and setuptools availability in the created environment, matching standard venv behavior and fixing any hook that depends on pip at runtime.

Fixes#61

uv venv does not install pip by default, unlike python -m venv. Hooks like mypy that internally call `python -m pip install` to fetch type stubs fail with "No module named pip" in the created environment. Passing --seed to uv venv restores pip/setuptools availability, matching standard venv behavior and fixing hooks that depend on pip at runtime. Fixestox-dev#61

gaborbernat · 2026-02-18T04:49:13Z

uv venv does not install pip into virtual environments by default, unlike python -m venv. Hooks such as mypy that internally call python -m pip install at runtime (e.g. to fetch missing type stubs) fail with No module named pip in the hook environment. This affects CI environments where pre-commit-uv manages hook installation.

Passing --seed to uv venv restores pip and setuptools availability in the created environment, matching standard venv behavior and fixing any hook that depends on pip at runtime.

Fixes#61

uv venv does not install pip by default, unlike python -m venv. Hooks like mypy that internally call `python -m pip install` to fetch type stubs fail with "No module named pip" in the created environment. Passing --seed to uv venv restores pip/setuptools availability, matching standard venv behavior and fixing hooks that depend on pip at runtime. Fixestox-dev#61

gaborbernat · 2026-02-18T04:49:13Z

uv venv does not install pip into virtual environments by default, unlike python -m venv. Hooks such as mypy that internally call python -m pip install at runtime (e.g. to fetch missing type stubs) fail with No module named pip in the hook environment. This affects CI environments where pre-commit-uv manages hook installation.

Passing --seed to uv venv restores pip and setuptools availability in the created environment, matching standard venv behavior and fixing any hook that depends on pip at runtime.

Fixes#61

uv venv does not install pip by default, unlike python -m venv. Hooks like mypy that internally call `python -m pip install` to fetch type stubs fail with "No module named pip" in the created environment. Passing --seed to uv venv restores pip/setuptools availability, matching standard venv behavior and fixing hooks that depend on pip at runtime. Fixestox-dev#61

gaborbernat · 2026-02-18T04:49:13Z

uv venv does not install pip into virtual environments by default, unlike python -m venv. Hooks such as mypy that internally call python -m pip install at runtime (e.g. to fetch missing type stubs) fail with No module named pip in the hook environment. This affects CI environments where pre-commit-uv manages hook installation.

Passing --seed to uv venv restores pip and setuptools availability in the created environment, matching standard venv behavior and fixing any hook that depends on pip at runtime.

Fixes#61

uv venv does not install pip by default, unlike python -m venv. Hooks like mypy that internally call `python -m pip install` to fetch type stubs fail with "No module named pip" in the created environment. Passing --seed to uv venv restores pip/setuptools availability, matching standard venv behavior and fixing hooks that depend on pip at runtime. Fixestox-dev#61

gaborbernat · 2026-02-18T04:49:13Z

uv venv does not install pip into virtual environments by default, unlike python -m venv. Hooks such as mypy that internally call python -m pip install at runtime (e.g. to fetch missing type stubs) fail with No module named pip in the hook environment. This affects CI environments where pre-commit-uv manages hook installation.

Passing --seed to uv venv restores pip and setuptools availability in the created environment, matching standard venv behavior and fixing any hook that depends on pip at runtime.

Fixes#61

uv venv does not install pip by default, unlike python -m venv. Hooks like mypy that internally call `python -m pip install` to fetch type stubs fail with "No module named pip" in the created environment. Passing --seed to uv venv restores pip/setuptools availability, matching standard venv behavior and fixing hooks that depend on pip at runtime. Fixestox-dev#61

gaborbernat · 2026-02-18T04:49:13Z

uv venv does not install pip into virtual environments by default, unlike python -m venv. Hooks such as mypy that internally call python -m pip install at runtime (e.g. to fetch missing type stubs) fail with No module named pip in the hook environment. This affects CI environments where pre-commit-uv manages hook installation.

Passing --seed to uv venv restores pip and setuptools availability in the created environment, matching standard venv behavior and fixing any hook that depends on pip at runtime.

Fixes#61

uv venv does not install pip by default, unlike python -m venv. Hooks like mypy that internally call `python -m pip install` to fetch type stubs fail with "No module named pip" in the created environment. Passing --seed to uv venv restores pip/setuptools availability, matching standard venv behavior and fixing hooks that depend on pip at runtime. Fixestox-dev#61

gaborbernat · 2026-02-18T04:49:13Z

uv venv does not install pip into virtual environments by default, unlike python -m venv. Hooks such as mypy that internally call python -m pip install at runtime (e.g. to fetch missing type stubs) fail with No module named pip in the hook environment. This affects CI environments where pre-commit-uv manages hook installation.

Passing --seed to uv venv restores pip and setuptools availability in the created environment, matching standard venv behavior and fixing any hook that depends on pip at runtime.

Fixes#61

uv venv does not install pip by default, unlike python -m venv. Hooks like mypy that internally call `python -m pip install` to fetch type stubs fail with "No module named pip" in the created environment. Passing --seed to uv venv restores pip/setuptools availability, matching standard venv behavior and fixing hooks that depend on pip at runtime. Fixestox-dev#61

gaborbernat · 2026-02-18T04:49:13Z

uv venv does not install pip into virtual environments by default, unlike python -m venv. Hooks such as mypy that internally call python -m pip install at runtime (e.g. to fetch missing type stubs) fail with No module named pip in the hook environment. This affects CI environments where pre-commit-uv manages hook installation.

Passing --seed to uv venv restores pip and setuptools availability in the created environment, matching standard venv behavior and fixing any hook that depends on pip at runtime.

Fixes#61

uv venv does not install pip by default, unlike python -m venv. Hooks like mypy that internally call `python -m pip install` to fetch type stubs fail with "No module named pip" in the created environment. Passing --seed to uv venv restores pip/setuptools availability, matching standard venv behavior and fixing hooks that depend on pip at runtime. Fixestox-dev#61

gaborbernat added the bug Something isn't working label Feb 18, 2026

gaborbernat enabled auto-merge (squash) February 18, 2026 04:49