Skip to content
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

Getting started with Python in VS Code suggestions #20383

Closed
minsa110 opened this issue Dec 14, 2022 · 3 comments · Fixed by #20457
Closed

Getting started with Python in VS Code suggestions #20383

minsa110 opened this issue Dec 14, 2022 · 3 comments · Fixed by #20457
Assignees
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug feature-request Request for new features or functionality info-needed Issue requires more information from poster needs PR Ready to be worked on verified Verification succeeded
Milestone

Comments

@minsa110
Copy link

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:

  1. 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)
  2. 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
    image
    image
  3. 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)
@minsa110 minsa110 added the feature-request Request for new features or functionality label Dec 14, 2022
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Dec 14, 2022
@brettcannon
Copy link
Member

Suggestion 3 is a duplicate of #20133 .

@karrtikr
Copy link

karrtikr commented Jan 4, 2023

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.

@karrtikr karrtikr added info-needed Issue requires more information from poster bug Issue identified by VS Code Team member as probable bug labels Jan 4, 2023
@karrtikr
Copy link

karrtikr commented Jan 4, 2023

Bug mentioned in 2. should be fixed with #20457.

@karrtikr karrtikr added area-environments Features relating to handling interpreter environments needs PR Ready to be worked on and removed triage-needed Needs assignment to the proper sub-team labels Jan 4, 2023
@karrtikr karrtikr added this to the January 2023 milestone Jan 4, 2023
@karrtikr karrtikr added the verification-needed Verification of issue is requested label Jan 24, 2023
@bhavyaus bhavyaus added verified Verification succeeded and removed verification-needed Verification of issue is requested labels Jan 25, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug feature-request Request for new features or functionality info-needed Issue requires more information from poster needs PR Ready to be worked on verified Verification succeeded
Projects
None yet
4 participants