Missing .pixi/envs produces a warning in a non-Python workspace #26223

Behaviour

Opening a non-Python repository produces this warning in the Python Output channel:

[warning] Dir "<workspace>/.pixi/envs" is not watchable (directory does not exist)

The repository does not use Python or Pixi and has no Pixi environment. The missing directory is expected, so the warning suggests a configuration problem where there is nothing to fix.

Expected behaviour

A missing optional Pixi environment directory should be skipped silently or logged at debug/trace level when the workspace does not use Pixi.

Steps to reproduce in the affected setup

1. Enable Python, Python Environments and Ruff in a VS Code WSL window (versions below).
2. Open a repository containing Markdown and TOML files, with no Python/Pixi project or .pixi/envs directory.
3. Let the extensions activate during workspace startup.
4. Check the Python Output channel for the warning above.

These describe the affected setup; I have not tested a clean-profile minimal reproduction.

Activation details

The extension-host log shows Ruff activating Python Environments through its API, followed by Python Environments activating Python:

ExtensionService#_doActivateExtension ms-python.vscode-python-envs, startup: false, activationEvent: 'api', root cause: charliermarsh.ruff
ExtensionService#_doActivateExtension ms-python.python, startup: false, activationEvent: 'api', root cause: ms-python.vscode-python-envs

The installed Ruff extension also declares activation for Markdown files. This explains how Python becomes active in this workspace without working on Python code.

Environment

Python project/interpreter version: not applicable to this repository.

Related issues and possible cause

• Switch logging for pixi search from error to warning #23710 reduced the missing-directory message from error to warning.
• Consider not logging warnings when not applicable (for pixi envs) #23901 requested suppressing irrelevant Pixi warnings and was closed by Restore pixi functionality only when Pixi is available #24319. Its discussion includes this exact directory warning.

The warning is still present in the installed Python 2026.8.0 extension. The upstream code also appears to retain a separate watcher path:

• getVirtualEnvRootDirs unconditionally returns <workspace>/.pixi/envs, which the PixiLocator constructor supplies to the watcher.
• FSWatchingLocator logs traceWarn when that directory does not exist.

The Pixi availability check in environment enumeration appears not to guard watcher initialization. Could the missing optional directory be handled without a warning?

Local paths are replaced with placeholders, and timestamps and unrelated logs are omitted.