|
9 | 9 | // Allow X11 apps to run inside the container |
10 | 10 | "DISPLAY": "${localEnv:DISPLAY}", |
11 | 11 | // Do the equivalent of "activate" the venv so we don't have to "uv run" everything |
| 12 | + "VIRTUAL_ENV": "/workspaces/${localWorkspaceFolderBasename}/.venv", |
12 | 13 | "PATH": "/workspaces/${localWorkspaceFolderBasename}/.venv/bin:${containerEnv:PATH}" |
13 | 14 | }, |
14 | 15 | "customizations": { |
15 | 16 | "vscode": { |
16 | 17 | // Set *default* container specific settings.json values on container create. |
17 | 18 | "settings": { |
| 19 | + // Use the container's python by default |
18 | 20 | "python.defaultInterpreterPath": "/workspaces/${localWorkspaceFolderBasename}/.venv/bin/python", |
| 21 | + // Don't activate the venv as it is already in the PATH |
19 | 22 | "python.terminal.activateEnvInCurrentTerminal": false, |
20 | 23 | "python.terminal.activateEnvironment": false, |
21 | | - "remote.autoForwardPorts": false |
| 24 | + // Workaround to prevent garbled python REPL in the terminal |
| 25 | + // https://github.com/microsoft/vscode-python/issues/25505 |
| 26 | + "python.terminal.shellIntegration.enabled": false |
22 | 27 | }, |
23 | 28 | // Add the IDs of extensions you want installed when the container is created. |
24 | 29 | "extensions": [ |
|
33 | 38 | } |
34 | 39 | }, |
35 | 40 | // Create the config folder for the bash-config feature and uv cache |
| 41 | + // NOTE: The uv cache can get large, DLS users should read |
| 42 | + // https://dev-guide.diamond.ac.uk/linux-user-environment/how-tos/disk-quota-troubleshooting |
36 | 43 | "initializeCommand": "mkdir -p ${localEnv:HOME}/.config/terminal-config ${localEnv:HOME}/.cache/uv", |
37 | 44 | "runArgs": [ |
38 | 45 | // Allow the container to access the host X11 display and EPICS CA |
|
0 commit comments