|
| 1 | +--- |
| 2 | +name: Bug Report |
| 3 | +about: Create a report to help us improve. |
| 4 | +title: '' |
| 5 | +labels: '' |
| 6 | +assignees: '' |
| 7 | + |
| 8 | +--- |
| 9 | + |
| 10 | +<!-- |
| 11 | +Please search existing issues first to avoid creating duplicates: |
| 12 | +https://github.com/microsoft/vscode-python-environments/issues |
| 13 | +--> |
| 14 | + |
| 15 | +## Environment data |
| 16 | + |
| 17 | +<!-- |
| 18 | +To find extension versions, open the VS Code Extensions panel and locate each |
| 19 | +extension from the list of installed extensions. The version appears next to the name. |
| 20 | +--> |
| 21 | + |
| 22 | +- Python Environments extension version: XXX |
| 23 | +- Python extension (`ms-python.python`) version: XXX |
| 24 | +- VS Code version (Help → About): XXX |
| 25 | +- OS and version: XXX |
| 26 | +- Python version (& distribution if applicable, e.g. Anaconda): XXX |
| 27 | +- Environment manager in use (`venv` / `conda` / `pyenv` / `poetry` / `pipenv` / `system` / `uv` / other): XXX |
| 28 | +- Shell (bash / zsh / fish / pwsh / cmd / other): XXX |
| 29 | +- Remote / container scenario (none / WSL / SSH Remote / Dev Container / Codespaces): XXX |
| 30 | +- Workspace type (single folder / multi-root / mono-repo): XXX |
| 31 | +- Is this a regression? If yes, last known working extension version: XXX |
| 32 | + |
| 33 | +## Repro Steps |
| 34 | + |
| 35 | +<!-- |
| 36 | +Please list the minimal steps needed to reproduce the issue, starting from a fresh |
| 37 | +VS Code window when possible. If the issue only reproduces with specific workspace |
| 38 | +contents (e.g. a `pyproject.toml`, `.venv`, `environment.yml`, `Pipfile`, `poetry.lock`, |
| 39 | +`.python-version`), please share a minimal example or describe the layout. |
| 40 | +
|
| 41 | +If the bug only reproduces with certain settings, please include the relevant entries |
| 42 | +from your `settings.json` (user and/or workspace). |
| 43 | +
|
| 44 | +Note: If a GIF or screenshot would help, consider tools like |
| 45 | +https://github.com/vkohaupt/vokoscreenNG, https://www.cockos.com/licecap/, |
| 46 | +https://github.com/phw/peek or https://www.screentogif.com/ . |
| 47 | +--> |
| 48 | + |
| 49 | +1. XXX |
| 50 | + |
| 51 | +## Expected behavior |
| 52 | + |
| 53 | +XXX |
| 54 | + |
| 55 | +## Actual behavior |
| 56 | + |
| 57 | +XXX |
| 58 | + |
| 59 | +## Logs |
| 60 | + |
| 61 | +<!-- |
| 62 | +Please include logs from the "Python Environments" output channel. |
| 63 | +
|
| 64 | +To capture verbose logs: |
| 65 | +1. Open the Output panel (View → Output). |
| 66 | +2. Select "Python Environments" from the channel dropdown in the upper-right. |
| 67 | +3. Click the gear / filter icon at the top of the Output panel and set the level to "Trace". |
| 68 | + (Alternatively: Command Palette → "Developer: Set Log Level…" → "Python Environments" → "Trace".) |
| 69 | +4. Reproduce the issue. |
| 70 | +5. Paste the relevant output below, or save it to a `.txt` file and attach it to the issue (preferred for long logs). |
| 71 | +
|
| 72 | +If the issue is about terminal activation, please also paste the exact terminal |
| 73 | +output where the problem occurs. |
| 74 | +--> |
| 75 | + |
| 76 | +``` |
| 77 | +XXX |
| 78 | +``` |
| 79 | + |
| 80 | +## Additional context |
| 81 | + |
| 82 | +<!-- |
| 83 | +Anything else that may help us reproduce: screenshots, videos, related issues, |
| 84 | +links to your project, workarounds you've tried, etc. |
| 85 | +--> |
0 commit comments