Hatch Code

An extension to manage Hatch environments through vscode-python-environments.

To make use of it, make sure your user settings contain "python.useEnvironmentsExtension": true.

Features

• List all configured Hatch environments
• Provide controls to set them as active environment for your project, activate them in a terminal, and delete them from disk
• Temporarily modify an environment’s packages using the configured installer
• Define a hatch.envInterpreter command for use in launch.json or tasks.json, see below

Since many actions currently use hatch run and therefore sync the environment, temporary package changes can be quickly undone, especially removing packages installed as dependencies. Persistent modifications to the installed packages should be done by editing Hatch’s envs configuration.

Commands

• hatch.envInterpreter: not an interactive command, but rather for use in launch.json or tasks.json via variable substitution, e.g. for command in tasks.json or python in launch.json:

  {  // launch.json
    "version": "0.2.0",
    "configurations": [
      {
        "name": "Python: Debug script",
        "type": "debugpy",
        "request": "launch",
        "python": "${input:scriptsInterpreter}",
        "program": "${file}",
      },
    ],
    "inputs": [
      {
        "id": "scriptsInterpreter",
        "type": "command",
        "command": "hatch.envInterpreter",
        "args": { "env": "scripts" },
      },
    ],
  }

  The command supports the following args:

  • env: name of the environment (defaults to "default")
  • workspace: path to the workspace root (defaults to the first currently open workspace)

  It can be used without going through inputs using just ${command:hatch.envInterpreter} to always use the default environment instead of the currently active one.

Extension Settings

• hatch.executable: path to the hatch executable (supports ~ expansion). Defaults to the output of which hatch.

Limitations

• It’s pretty unclear which environments exist on disk and which don’t
• We list internal envs that users don’t usually interact with, such as hatch-uv and hatch-build