python / python/cpython

On Windows, VENV does not copy pip module into a new created virtual environments

Abierto
#139,018 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

stdlib topic-venv type-bug
Lenguaje dominante
Python
Estrellas
77.2k
Forks
35.9k
Métricas de merge de PR
Métricas de PR pendientes

Descripción

Bug report

Bug description:

When creating a new isolated environment via VENVE, module pip is not installed and does not exist in Lib/site-packages. The command pip is available but still operates on non-virtual environment level.

Specification
  • Windows 10 Home (22H2)
  • PowerShell 7.5.3
  • Python 3.13.7
  • Launcher (py.exe).
Steps to reproduce the issue
  • Run py -m venv .venv
  • Activate environment: .\ .venv\Scripts\Activate.ps1
  • Try to upgrade pip: python -m pip install pip --upgrade
  • Python will report the error that pip is not installed.

Other distribution s.a. 3.12 and 3.11 have the same issue.

Description

I simply run the following command py -m venv .venv to create a new environment, followed by activation .venv\Scripts\Activate.ps1. I've got a new prompt (.venv) PS D ...> . The Get-Command python indicates the correct path to python.exe: <local path>\.venv\Scripts\python.exe.

Here's the problem. After activating new environment, while pip is still available as a standalone program, it does not work on a local level. If I try to run pip install numpy --dry-run, I get the report

Requirement already satisfied: numpy in <user>\appdata\local\programs\python\python313\lib\site-packages (2.3.3)

I believe pip should work on a local level. BTW, if I run the command Get-Command pip, the path to pip is

<User>\AppData\Local\Programs\Python\Python313\Scripts\pip.exe
Impossible to install new modules

This obviously leads to the problem of not being able to install new modules in newly created environments because pip is missing. For instance python -m pip install pip --upgrade issues the error

`<local path>\.venv\Scripts\python.exe: No module named pip

while python still works as expected, that is Get-Command python outputs

<local path>\.venv\Scripts\python.exe

I can also run Get-Children -Recurse -Path ".venv/" to check local Lib/site-packages

    Directory: <Local Path>\.venv

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d----          16/09/2025    12:20                Include
d----          16/09/2025    12:20                Lib
d----          16/09/2025    12:20                Scripts
-a---          16/09/2025    12:20             71 .gitignore
-a---          16/09/2025    12:20            338 pyvenv.cfg

    Directory: <Local Path>\.venv\Lib

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d----          16/09/2025    12:20                site-packages

    Directory: <Local Path>\.venv\Scripts

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a---          16/09/2025    12:20           2208 activate
-a---          16/09/2025    12:20           1022 activate.bat
-a---          16/09/2025    12:20           2281 activate.fish
-a---          06/08/2025    16:16           9031 Activate.ps1
-a---          06/08/2025    16:14            393 deactivate.bat
-a---          06/08/2025    16:15         255320 python.exe
-a---          06/08/2025    16:15         251736 pythonw.exe

    Directory: <Local Path>\__pycache__

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a---          29/07/2024    16:12          15096 backup.cpython-312.pyc

but the folder Lib/site-packages is empty. please, note Get-Children -Recurse ignores empty folders in further iteration.


Possible workarounds

The only working workaround is to copy pip and pip-25.2.dist-info from global Lib/site-packages into isolated environment's Lib/site-packages.

CPython versions tested on:

CPython main branch

Operating systems tested on:

Windows

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

Comienza con el punto de entrada py -m venv .venv y reproduce los comandos de Windows PowerShell descritos en el informe. Comprueba cómo el nuevo entorno inicializa pip y verifica el resultado con respecto al directorio vacío Lib/site-packages; se considera terminado cuando pip está disponible a través del Python del entorno en lugar de la instalación global.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
python
Área
tooling
Tipo de issue
Error
Dificultad
3/5
Tiempo estimado
1-2 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
45/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.