Skip to content

Actions: microsoft/vscode-python-environments

Actions

Issue labels

Actions

Loading...
Loading

Show workflow options

Create status badge

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

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
Add ability to exclude Python Environment from Python Extension Issue labels #161: Issue #1043 opened by DonJayamanne
15s
15s
Investigate a potential opinionated package management workflow Issue labels #160: Issue #1042 opened by cwebster-99
15s
15s
documentation for searchPaths Issue labels #159: Issue #1041 opened by eleanorjboyd
17s
17s
The new python environment extension does not activate the environment when launching a task Issue labels #158: Issue #1040 opened by albertino87
21s
21s
Bug: Command 'python.getRecommendedEnvironment' already exists in multi-root workspace Issue labels #157: Issue #1039 opened by ameicler
21s
21s
Support symbolic link for python.venvPath Issue labels #156: Issue #1038 opened by anemele
22s
22s
git clean in a python project triggers invalid python notification Issue labels #155: Issue #1037 opened by karthiknadig
18s
18s
Bash shell does not activate venv on subsequent launches Issue labels #154: Issue #359 reopened by anthonykim1
16s
16s
open terminal from global python activates wrong environment Issue labels #153: Issue #1035 opened by eleanorjboyd
40s
40s
[Bug] Conda Environments not found (windows) Issue labels #152: Issue #1034 opened by riedgar-ms
18s
18s
Poetry environments not detected starting with Python Environments extension v1.11.1282035 and later Issue labels #151: Issue #1033 opened by cakeller98
15s
15s
Issues working on workspaces with multiple components subfolders, each with it's own venv. Issue labels #150: Issue #1032 opened by Carbaz
16s
16s
Feature Request: Conditional Activity Bar Icon Visibility Based on Project Type Issue labels #149: Issue #1028 opened by raufzer
13s
13s
launching a local integrated terminal from wsl will look for linux location for venv Issue labels #148: Issue #1027 opened by amunger
15s
15s
.\vscode-python\deactivate.ps1 in PowerShell_profile.ps1 breaks activation Issue labels #147: Issue #1026 opened by amunger
23s
23s
Python env auto-activation regression: Terminal no longer activates unless legacy settings are enabled Issue labels #146: Issue #1025 opened by JVSCHANDRADITHYA
20s
20s
[Python Environments] Issue labels #145: Issue #1024 opened by engayoya2007-del
15s
15s
Consider caching for shellStartup profiles Issue labels #144: Issue #1023 opened by anthonykim1
22s
22s
Add tests for shell startup activation Issue labels #143: Issue #1019 opened by anthonykim1
29s
29s
uv-managed workspaces don't appear in the extension yet Issue labels #142: Issue #1017 opened by zsol
16s
16s
Incorrect terminal name when running Python file Issue labels #141: Issue #1016 opened by Sharl0tteIsTaken
14s
14s
envFile configuration wrongly includes a trailing comment in environment variable value Issue labels #140: Issue #1014 opened by Magicbeanbuyer
19s
19s
Python interpreter option goes missing Issue labels #139: Issue #1013 opened by wangruoyuyuyu
18s
18s
how to auto-activate env (without the command) prior to running code? Issue labels #138: Issue #1011 opened by szw0407
16s
16s
Version 1.12 Failed to identify anaconda environment Issue labels #137: Issue #1002 opened by steveshaoucsb
15s
15s