API: create environment with name by edvilme · Pull Request #1802 · microsoft/vscode-python-environments

Eduardo Villalpando Mello (edvilme) · 2026-09-22T00:54:08Z

This pull request introduces a new optional name field to the CreateEnvironmentOptions for the @vscode/python-environments API, allowing API consumers to specify a desired environment name when creating Python environments. The implementation ensures that provided names are validated and integrated into both venv and conda environment creation flows. Documentation and versioning are updated accordingly.

API and Documentation Updates:

Added an optional name property to CreateEnvironmentOptions, enabling consumers to request a specific environment name during creation. The documentation (docs/README.md) and changelog (api/CHANGELOG.md) are updated to reflect this new feature. [1] [2] [3] [4]
Bumped package version to 1.5.0 in package.json and package-lock.json. [1] [2]

Validation and Core Logic:

Implemented validation for the name field to ensure it is a non-empty path segment and does not contain invalid characters (e.g., ., .., /, This pull request introduces a new optional namefield to theCreateEnvironmentOptionsfor the@vscode/python-environments` API, allowing API consumers to specify a desired environment name when creating Python environments. The implementation ensures that provided names are validated and integrated into both venv and conda environment creation flows. Documentation and versioning are updated accordingly.

API and Documentation Updates:

Added an optional name property to CreateEnvironmentOptions, enabling consumers to request a specific environment name during creation. The documentation (docs/README.md) and changelog (api/CHANGELOG.md) are updated to reflect this new feature. [1] [2] [3] [4]
Bumped package version to 1.5.0 in package.json and package-lock.json. [1] [2]

Validation and Core Logic:

, or null bytes).

Venv Environment Creation:

Updated venv creation flows to accept and use the supplied name, including validation for existing directories and proper handling in both quick and step-based flows. The state management is enhanced to track if the name was supplied by the user. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

Conda Environment Creation:

Extended conda environment creation flows to support the optional name parameter, ensuring correct flow control, state management, and back-navigation logic. The implementation also ensures that the environment is created with the requested name if provided. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

Bill Schnurr (bschnurr) · 2026-09-22T16:46:46Z

🔒 Automated review in progress — Bill Schnurr (@bschnurr) is auto-reviewing this PR.

Rich Chiodo (rchiodo)

I feel like the name needs to be validated to contain allowed path characters.

For example, I don't think a name of ..\..\ would work very well.

Bill Schnurr (bschnurr)

Approved via Review Center.

Stella Huang (StellaHuang95)

Approved via Review Center.

Eleanor Boyd (eleanorjboyd)

The updated API contract says managers should honor a supplied name, but:

SysPythonManager.create ignores the options entirely.
InlineScriptEnvManager.create ignores name and creates or reuses a hash-keyed environment.

Eduardo Villalpando Mello (edvilme) · 2026-10-02T21:10:45Z

The updated API contract says managers should honor a supplied name, but:

SysPythonManager.create ignores the options entirely.

InlineScriptEnvManager.create ignores name and creates or reuses a hash-keyed environment.

Related: #1874

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: a9796987-f9b0-451b-a3cd-35d8a950eac8

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Advertise environment.create.named for venv and Conda, keep legacy and unsupported managers disabled, and route named creation through scoped capability checks. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 9606a9cf-3e6e-458f-a6e1-6707e4a490c7

Bill Schnurr (bschnurr) · 2026-10-15T20:18:36Z