Skip to content

Actions: microsoft/vscode-python-environments

Actions

Issue labels

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
issue-labels.yml
194 workflow runs
194 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

shellStartup does not activate when in WSL Issue labels #44: Issue #865 reopened by karthiknadig
24s
24s
Shell integration wasn't available to activate for wsl scenario. Issue labels #43: Issue #885 opened by anthonykim1
23s
23s
Issue labels Issue labels #42: opened by anthonykim1
21s
21s
Environment configuration change warning shows up even if there is no change in environment Issue labels #41: Issue #883 opened by karthiknadig
20s
20s
shell integration says its not available in wsl) shellShartup update profile modal shows up for each terminal Issue labels #40: Issue #882 opened by karthiknadig
30s
30s
Fix lint warnings Issue labels #39: Issue #881 opened by Tyriar
19s
19s
Default interpreter Path does not respect .bat file when executing scripts Issue labels #38: Issue #541 reopened by rzhao271
22s
22s
Environment fails to activate when environment path contains special characters Issue labels #37: Issue #876 opened by lukas-lang
21s
21s
Python environment not activating and working dir not correct when using scratchpad Issue labels #36: Issue #875 opened by albertino87
19s
19s
Python architecture information missing for conda envs Issue labels #35: Issue #874 opened by BegiraTool
15s
15s
Feature: Global and Workspace Python Environment Search Paths Issue labels #34: Issue #870 opened by eleanorjboyd
16s
16s
Integrated terminal activates base conda environment instead of configured environment Issue labels #33: Issue #869 opened by AntonioDEM
24s
24s
Detected Python version is wrong and may affect Python Debugger extension. Issue labels #32: Issue #868 opened by KuRRe8
18s
18s
not run in python in teminal Issue labels #31: Issue #866 opened by Faizan-36
20s
20s
shellStartup does not activate when in WSL Issue labels #30: Issue #865 opened by karthiknadig
27s
27s
conda run --name env_name file.py does not work Issue labels #29: Issue #862 opened by matte-esse
15s
15s
Settings Review: Python ext & Python Envs ext Issue labels #28: Issue #861 opened by eleanorjboyd
25s
25s
Conda environment manager does not start kernel Issue labels #27: Issue #859 opened by anzakhangale47-wq
21s
21s
python environments finds out-of-source python in another .venv (Windows) Issue labels #26: Issue #858 opened by schwaerz
18s
18s
Terminal opens prematurely with PET Resolve Environment command Issue labels #25: Issue #855 opened by eleanorjboyd
22s
22s
Error refreshing packages: Extension uses system Python instead of selected Conda environment in WSL2 Issue labels #24: Issue #653 reopened by karthiknadig
24s
24s
Incorrectly loads uv interpreters Issue labels #23: Issue #667 reopened by karthiknadig
21s
21s
Env extension doesn't work at all Issue labels #22: Issue #848 opened by felipediefenbach
25s
25s
Copilot chat cannot detect Python packages installed in the selected Conda Environment Issue labels #21: Issue #847 opened by klaus3331
17s
17s
CTRL-C is immediately issued upon run, execution gets cancelled by activation command Issue labels #20: Issue #640 reopened by anthonykim1
21s
21s