Skip to content

[Python Environments] "venv" #1738

Closed as not planned
Closed as not planned
[Python Environments] "venv"#1738
Assignees
StellaHuang95
Labels
info-neededIssue requires more information from poster~info-neededIssue requires more information from poster (with bot comment)

Description

@22bba015
22bba015
opened on Mar 3, 2026

Type: Feature Request

i did not get my venv throught create python environment
Environment Information 
Extension Version: 1.20.1
Python Extension Version: 2026.2.0

Registered Environment Managers (2):
  - ms-python.python:system (Global)
  - ms-python.python:venv (venv)

Total Available Environments: 3
Environment Details:
  1. Python 3.14 (64-bit) (3.14.3) - C:\Users\tls\AppData\Local\Programs\Python\Python314\python.exe
  2. Python 3.13 (3.13.12.final.0) - C:\Users\tls\AppData\Local\Microsoft\WindowsApps\python3.13.exe
  3. Python 3.13 (64-bit) (3.13.12) - C:\Users\tls\AppData\Local\Programs\Python\Python313\python.exe

Python Projects (1):
  1. c:\Users\tls\python master
     Environment: Python 3.14 (64-bit)

Extension Settings:
  Default Environment Manager: ms-python.python:venv
  Default Package Manager: ms-python.python:pip
Auto-activation is "command". Activation based on first 'py-env.terminal.autoActivationType' setting which is 'command' and 'python.terminal.activateEnvironment' if the first is undefined which is 'true'.

VS Code version: Code 1.109.5 (072586267e68ece9a47aa43f8c108e0dcbf44622, 2026-02-19T19:43:32.382Z)
OS version: Windows_NT x64 10.0.26100
Modes:

Activity

  1. vs-code-engineering
    assigned
    Martin Aeschlimann (aeschli)
    on Mar 3, 2026
  2. Martin Aeschlimann (aeschli)
    assigned
    Karthik Nadig (karthiknadig)
    and unassigned
    Martin Aeschlimann (aeschli)
    on Mar 3, 2026

  3. HUMANCODERMJ commented on Mar 10, 2026

    @HUMANCODERMJ
    Manas Jha (HUMANCODERMJ)
    on Mar 10, 2026

    22bba015 I created the virtual environment with python3 -m venv .venv command, and I was facing the same issue as you mentioned, so I went into the json and made the python.venvFolders list object empty, then vscode was able to read the virtual environment.

    Image
  4. Karthik Nadig (karthiknadig)
    removed their assignment
    on Aug 25, 2026
  5. Karthik Nadig (karthiknadig)
    transferred this issue frommicrosoft/vscodeon Aug 25, 2026
  6. github-actions
    added
    triage-needed
    on Aug 25, 2026
  7. vs-code-engineering
    added
    ~info-neededIssue requires more information from poster (with bot comment)
    and removed
    triage-needed
    on Aug 25, 2026
  8. vs-code-engineering
    assigned
    Karthik Nadig (karthiknadig)
    on Aug 25, 2026
  9. Karthik Nadig (karthiknadig)
    assigned
    Stella Huang (StellaHuang95)
    and unassigned
    Karthik Nadig (karthiknadig)
    on Aug 25, 2026

  10. StellaHuang95 commented on Aug 25, 2026

    @StellaHuang95
    Stella Huang (StellaHuang95)
    on Aug 25, 2026
    Contributor

    22bba015 Manas Jha (@HUMANCODERMJ) Thanks for reporting the issue. Could you please try the following things and provide some additional info to help us diagnose?

    1. Please update Python Environments to the latest stable release and retry in a small, clean workspace.
    2. Which exact command and options did you use? Is it Python: Create Environment, the Environment Managers view, Quick Create, or Custom Create?
    3. Did any notification/error appeared? After the failure, do .venv\pyvenv.cfg and .venv\Scripts\python.exe exist? Also check for .venv-1, since the extension creates that name when .venv already exists.
    4. Please provide the complete Output → Python Environments log from window reload through creation and refresh. Thanks.

  11. eleanorjboyd commented on Sep 23, 2026

    @eleanorjboyd
    Eleanor Boyd (eleanorjboyd)
    on Sep 23, 2026
    Member

    🤖 Thanks for the report. To determine whether environment creation failed or the created environment was not discovered, please retry with the latest stable Python Environments release in a small, clean workspace and provide:

    • the exact command and options used (Python: Create Environment, Quick Create, Custom Create, or the Environment Managers view);
    • the environment manager and shell, plus the current python.venvFolders value;
    • any notification or error, and whether .venv\pyvenv.cfg, .venv\Scripts\python.exe, or a .venv-1 directory exists afterward; and
    • the complete trace-level log from the Python Environments output channel, starting with a window reload and continuing through creation and refresh.

    Issues marked info-needed are automatically closed after 7 days without a reply.

  12. Eleanor Boyd (eleanorjboyd)
    added
    info-neededIssue requires more information from poster
    on Sep 23, 2026
  13. Eleanor Boyd (eleanorjboyd)
    closed this as not plannedon Sep 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

info-neededIssue requires more information from poster~info-neededIssue requires more information from poster (with bot comment)

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions