Skip to content

Actions: microsoft/vscode-python-environments

Actions

Issue labels

Actions

Loading...
Loading

Show workflow options

Create status badge

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

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

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
Support --system-site-packages Issue labels #19: Issue #846 opened by DervishD
27s
27s
When using venv or global python environment, a new terminal can always start with a conda base instead of performing conda deactivate Issue labels #18: Issue #845 opened by gaoren002
15s
15s
Tasks do not pick up assigned environment. Issue labels #17: Issue #840 opened by johncuyle
26s
26s
How can I avoid using ”conda run“ for executing my code? Issue labels #16: Issue #839 opened by syhgzz
18s
18s
Removing --live-stream from conda run causes EOF for input() Issue labels #15: Issue #838 opened by rhewy
19s
19s
Bug: environment being used differs from the one being displayed Issue labels #14: Issue #836 opened by FIGIO55
17s
17s
set python.terminal.executeInFileDir not working, python file run earlier than cd command Issue labels #13: Issue #835 opened by kaala
15s
15s
vscode指定环境时默认运行的不存在的文件 Issue labels #12: Issue #834 opened by bl201112
21s
21s
The chosen python interpreter is not written to workspace's .vscode settings.json file Issue labels #11: Issue #833 opened by rhewy
18s
18s