python / python/cpython

venv on Windows 11 with Python 3.13.7 includes global paths in sys.path despite include-system-site-packages = false, causing packages to be installed globally instead of in the venv

Ouverte
#138,691 5 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

pending stdlib topic-venv type-bug
Langage dominant
Python
Étoiles
77.2k
Forks
35.9k
Métriques de merge des PR
Métriques de PR en attente

Description

Bug report

Bug description:
Description

When creating and activating a virtual environment with Python 3.13.7 on Windows 11, sys.path includes global Python paths (e.g., C:\Program Files\Python313\python313.zip, C:\Program Files\Python313\DLLs, etc.), even though pyvenv.cfg has include-system-site-packages = false. This causes python -m pip install <package> to install packages to the global site-packages (C:\Program Files\Python313\Lib\site-packages) instead of the virtual environment's site-packages.

This breaks virtual environment isolation, requiring --target for every install, which is not the expected behavior.

Steps to Reproduce
  1. Install Python 3.13.7 from the official Windows installer, ensuring "Add python.exe to PATH" is checked.

  2. Open PowerShell 7.5.2.

  3. Create a test directory and virtual environment:
    mkdir test_venv_bug
    cd test_venv_bug
    python -m venv .venv

  4. Activate the virtual environment:
    ..venv\Scripts\Activate.ps1

  5. Check sys.path:
    python -c "import sys; print('\n'.join(sys.path))"

Expected: Only venv paths (e.g., C:\path\to\test_venv_bug\.venv, C:\path\to\test_venv_bug\.venv\Lib\site-packages).

  1. Check pyvenv.cfg (should have include-system-site-packages = false):
    Get-Content .venv\pyvenv.cfg

  2. Install a test package:
    python -m pip install requests

  3. Verify installation location:
    python -m pip list
    Get-ChildItem -Path .venv\Lib\site-packages | findstr requests
    Get-ChildItem -Path 'C:\Program Files\Python313\Lib\site-packages' | findstr requests

Expected: requests in .venv\Lib\site-packages; nothing in global.

Expected Behavior
  • sys.path should only include virtual environment paths (no global C:\Program Files\Python313* paths).
  • python -m pip install should install to .venv\Lib\site-packages.
Actual Behavior
  • sys.path includes global paths:
    • C:\Program Files\Python313\python313.zip
    • C:\Program Files\Python313\DLLs
    • C:\Program Files\Python313\Lib
    • C:\Program Files\Python313
    • C:\Users\jdstr\Documents\GitHub\ndx_scalper.git.venv_ndx_scalper
    • C:\Users\jdstr\Documents\GitHub\ndx_scalper.git.venv_ndx_scalper\Lib\site-packages
  • python -m pip install requests installs to global site-packages (C:\Program Files\Python313\Lib\site-packages), with warnings like "Target directory C:\Program Files\Python313\Lib\site-packages\certifi already exists."
  • python -m pip list in venv shows only pip; packages are missing in venv.
Environment
  • Python version: 3.13.7 (installed via official Windows installer)
  • OS: Windows 11 24H2 (Build 26100.5074)
  • Shell: PowerShell 7.5.2
  • pyvenv.cfg contents:

home = C:\Program Files\Python313
include-system-site-packages = false
version = 3.13.7
executable = C:\Program Files\Python313\python.exe
command = C:\Program Files\Python313\python.exe -m venv C:\Users\jdstr\Documents\GitHub\ndx_scalper.git.venv_ndx_scalper

  • Activated venv prompt: (.venv) PS ...
  • Get-Command python and Get-Command pip point to venv Scripts\python.exe and Scripts\pip.exe.
Additional Notes
  • Using --target=.venv\Lib\site-packages works as a workaround, but it's cumbersome.
  • Searched GitHub issues and Stack Overflow—no exact match, but similar to older Windows venv path leaks (e.g., pip #11154).
  • No antivirus or custom configs interfering (standard setup).
Minimal Reproducible Example

See "Steps to Reproduce" above. The test directory can be zipped and attached if needed.

Thanks for looking into this—it's breaking venv isolation on Windows.

CPython versions tested on:

3.13

Operating systems tested on:

Windows

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Piste de recherche

Commencez par reproduire le rapport avec python -m venv, le Scripts\python.exe activé et l’environnement Windows Python 3.13.7 indiqué. Comparez sys.path, pyvenv.cfg et les destinations signalées par python -m pip ; c’est terminé lorsque les chemins système sont exclus quand include-system-site-packages = false et que les installations restent dans la venv.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
python
Domaine
operating-systems, tooling
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
42/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.