From 652f4d6d090e462587282d0436c55785f64b1b25 Mon Sep 17 00:00:00 2001 From: RT Date: Sun, 9 Aug 2026 20:11:18 -0500 Subject: [PATCH] Record the Python project config VS Code wrote for MECHSPECSHEET Side-effect of configuring a Python environment while building the mech spec tooling. Harmless to keep: the scripts are standard-library only and need no venv, so this just stops VS Code re-prompting. Worth knowing that this same file sets files.eol to CRLF workspace-wide, which is right for the game content but also applies to newly created files -- it is why the MECHSPECSHEET scripts were born with CRLF shebangs and had to be normalised to LF before they would execute directly. Co-authored-by: Claude Opus 5 (Anthropic) Co-authored-by: GitHub Copilot --- .vscode/settings.json | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/.vscode/settings.json b/.vscode/settings.json index da1e4ab5..663c6887 100644 --- a/.vscode/settings.json +++ b/.vscode/settings.json @@ -9,5 +9,12 @@ // Preserve the original Windows CRLF line endings (Git's * -text in // .gitattributes also prevents conversion, but this keeps VS Code consistent). - "files.eol": "\r\n" + "files.eol": "\r\n", + "python-envs.pythonProjects": [ + { + "path": ".", + "envManager": "ms-python.python:venv", + "packageManager": "ms-python.python:pip" + } + ] }