You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Getting started with Python in VS Code suggestions #20383
I was trying out the getting started experience on my new Windows machine and wanted to share a couple of feature suggestions. I only installed VS Code (no Python on my machine, and no extensions on VS Code).
Particularly for the step where VSC leads the user to the Windows store to install Python on their machine, can we consider:
Letting the user know they need to reload VS Code in the "please install Python" message (or else, users still can't execute their code even after installation has finished)
Better managing the interpreter list after the initial Python installation from Windows store. For context, when I installed Python from Windows store (as VSC suggested), I got two entries in the interpreter list / kernel picker which was confusing
Prompting the Python: Create Environment command when the user tries to run Python code but only has global Python environment (also applying to .ipynb files)
Letting the user know they need to reload VS Code in the "please install Python" message (or else, users still can't execute their code even after installation has finished)
Users need not reload VSCode for the Windows store interpreter to show up. It should ideally automatically show up when the interpreter list is opened. Was this not the case?
Bug mentioned in 2. only happens if window is reloaded.
Activity
brettcannon commentedon Dec 15, 2022
Suggestion 3 is a duplicate of #20133 .
karrtikr commentedon Jan 4, 2023
Users need not reload VSCode for the Windows store interpreter to show up. It should ideally automatically show up when the interpreter list is opened. Was this not the case?
Bug mentioned in
2.only happens if window is reloaded.karrtikr commentedon Jan 4, 2023
Bug mentioned in
2.should be fixed with #20457.