-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Insights: microsoft/vscode-python
Overview
Could not load contribution data
Please try again later
1 Release published by 1 person
-
v2025.6.0
published
May 8, 2025
4 Pull requests merged by 3 people
-
Fix msys2 venv path
#25062 merged
May 13, 2025 -
Fix env error handling
#25049 merged
May 12, 2025 -
chore: lock down workflows
#25047 merged
May 9, 2025 -
Added pylock to activationevents
#25025 merged
May 7, 2025
1 Pull request opened by 1 person
-
[RFC] watch pyrefly settings
#25041 opened
May 7, 2025
10 Issues closed by 7 people
-
MSYS2 (MinGW32/64 or UCRT64) fails on Create virtual environment .venv
#24792 closed
May 13, 2025 -
Unable to run Django tests via Sidebar
#25056 closed
May 12, 2025 -
A failure to find an environment prevents Pylance from loading
#24211 closed
May 12, 2025 -
BiruleibinhoTest
#25055 closed
May 12, 2025 -
Stuck on Reactivating Terminals
#25053 closed
May 12, 2025 -
reactivating terminal showing
#25046 closed
May 9, 2025 -
Activate on finding pylock.toml
#25016 closed
May 7, 2025 -
python process will be killed when project window activating conda environment
#25009 closed
May 7, 2025 -
Python: Iteration Plan for April 2025
#24969 closed
May 7, 2025
9 Issues opened by 9 people
-
Python venv dependencies are not working with code completion
#25063 opened
May 13, 2025 -
Having pygls.protocol.json_rpc ValueError after updating to 2025.6.0 from 2025.4.0
#25060 opened
May 13, 2025 -
Wrong python selected after select interpreter
#25061 opened
May 13, 2025 -
python.analysis.autoFormatStrings settings should work in python notebook cells as well as plain .py files
#25059 opened
May 13, 2025 -
Do not fail test discovery on failure
#25058 opened
May 13, 2025 -
Incorrect PATH after selecting interpreter
#25048 opened
May 10, 2025 -
[vscode ver. 1.100] Python environment incorrectly activated
#25051 opened
May 10, 2025 -
Exposed API updateActiveEnvironmentPath outside workspace
#25045 opened
May 9, 2025 -
"ModuleNotFoundError: No module named 'packaging'" occurs when running unit tests
#25044 opened
May 9, 2025
14 Unresolved conversations
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
Environment Activation Fails: Direct Path to conda.bat Used Instead of conda Command After 2/7 Extension Update
#24801 commented on
May 7, 2025 • 0 new comments -
使用中文Command"Python.setinterpreter"not found
#25040 commented on
May 7, 2025 • 0 new comments -
Cannot run unittest in parallel anymore
#24829 commented on
May 7, 2025 • 0 new comments -
Kernel is lost in the middle of working with a notebook
#25042 commented on
May 8, 2025 • 0 new comments -
Missing brackts around virtual environment name in command prompt
#24917 commented on
May 8, 2025 • 0 new comments -
Problem executing multiple lines of code: ... versus >>>
#25043 commented on
May 8, 2025 • 0 new comments -
Python interpreter loading stuck
#24324 commented on
May 8, 2025 • 0 new comments -
The following extensions want to relaunch the terminal to contribute to its environment
#24822 commented on
May 9, 2025 • 0 new comments -
Run Selection/Line in already active python interpreter terminal rather than opening a new terminal
#24960 commented on
May 10, 2025 • 0 new comments -
Actived Python Environment only partially works
#25036 commented on
May 10, 2025 • 0 new comments -
Debugging leaves terminal in conda's Base environment instead of selected (interpreter's) conda environment
#25023 commented on
May 11, 2025 • 0 new comments -
Test discovery failure / regression for uniitest
#24578 commented on
May 11, 2025 • 0 new comments -
set python.terminal.executeInFileDir not working, python file run earlier than cd command
#25024 commented on
May 13, 2025 • 0 new comments -
Implement copying python import path from opened file
#25026 commented on
May 10, 2025 • 0 new comments