René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Missing leading semicolon when appending to PATH on Windows","articleBody":"**Type:** Bug\n\n**Context:**\n- VS Code version: 1.106.3 (user setup)\n- Extension version: ``2025.16.0``\n- OS: Windows 11 Enterprise 24H2 (26100.7171)\n- Shell: PowerShell 7.5.4\n- UV .venv (``uv 0.9.9 (4fac4cb7e 2025-11-12)``)\n\n**Behaviour:**\n\nWhen the debugpy extension appends its path to the ``PATH`` environment variable, it does not check if the existing PATH ends with a semicolon. If another tool (e.g., Bun) writes a PATH entry without a trailing semicolon, the paths get concatenated:\n```\nC:\\Users\\ggrondin.ext\\.bun\\binc:\\Users\\ggrondin.ext\\.vscode\\extensions\\ms-python.debugpy-2025.16.0-win32-x64\\bundled\\scripts\\noConfigScripts\n```\n\n**Expected:**\n\nThe extension should either:\n- Prepend a semicolon before adding its path, or\n- Check if the existing PATH ends with a semicolon and add one if missing\n\n**Steps to reproduce:**\n\n1. Have a PATH entry that does not end with a semicolon (e.g., current version of bun).\n2. Open a Python project with a venv in VSCode (e.g, current version of uv (``uv 0.9.9 (4fac4cb7e 2025-11-12)``)).\n3. Open an integrated terminal.\n4. Check ``$env:PATH`` — the paths are concatenated without separator.\n\n**Note:**\n\nThis might be related to (but probably different from) #740 which fixed double semicolons (``;;``). This issue is about the missing leading semicolon when appending (most probably).\n\nRelated: https://github.com/oven-sh/bun/issues/16811","author":{"url":"https://github.com/GGLinnk-ReadOnly","@type":"Person","name":"GGLinnk-ReadOnly"},"datePublished":"2025-12-03T09:18:25.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/882/vscode-python-debugger/issues/882"}