Skip to content

Issues: microsoft/vscode-python-environments

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

Suggest pinned package dependency updates on pyproject.toml feature-request Request for new features or functionality
#165 opened Feb 7, 2025 by jzazo
Update requirement.txt if available when using venv feature-request Request for new features or functionality needs spike
#146 opened Jan 29, 2025 by karthiknadig
Error refreshing packages error while running command in empty folder bug Issue identified by VS Code Team member as probable bug
#143 opened Jan 28, 2025 by rzhao271 February 2025
pythonGetPackages is too verbose bug Issue identified by VS Code Team member as probable bug
#142 opened Jan 28, 2025 by rzhao271 February 2025
#pythonGetPackages does not always produce expected output bug Issue identified by VS Code Team member as probable bug
#141 opened Jan 28, 2025 by isidorn February 2025
Add support for search paths for venvs feature-request Request for new features or functionality
#104 opened Jan 4, 2025 by Ninecr
relative paths not handled when installing packages from workplace dependencies (requirements.txt) bug Issue identified by VS Code Team member as probable bug
#82 opened Dec 12, 2024 by kristapratico
Extension support for environment managers feature-request Request for new features or functionality help wanted Issues identified as good community contribution opportunities
#79 opened Dec 11, 2024 by karthiknadig
Accessibility: Several sub-components in environment manager lacks accessibility bug Issue identified by VS Code Team member as probable bug
#61 opened Dec 4, 2024 by anthonykim1
Switching interpreter to global in environment manager doesn't deactivate previously activated .venv bug Issue identified by VS Code Team member as probable bug
#60 opened Dec 3, 2024 by anthonykim1
Refresh packages after installation from a terminal feature-request Request for new features or functionality
#57 opened Dec 3, 2024 by eleanorjboyd
re-select "set as workspace env" does nothing bug Issue identified by VS Code Team member as probable bug
#58 opened Dec 3, 2024 by eleanorjboyd
Add support for fallback venv creation with microvenv or uv feature-request Request for new features or functionality
#42 opened Dec 3, 2024 by karthiknadig
Show create venv when users attempt to install packages to global feature-request Request for new features or functionality
#41 opened Dec 3, 2024 by karthiknadig
Don't show activate button on tasks bug Issue identified by VS Code Team member as probable bug
#27 opened Nov 22, 2024 by karthiknadig
ProTip! Add no:assignee to see everything that’s not assigned.