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

Improvements to getting started experience for DS #1127

Closed
DonJayamanne opened this issue Feb 7, 2020 · 4 comments
Closed

Improvements to getting started experience for DS #1127

DonJayamanne opened this issue Feb 7, 2020 · 4 comments
Labels
feature-request Request for new features or functionality notebook-getting-started

Comments

@DonJayamanne
Copy link
Contributor

Should we consider having some kind of a workflow that'll help users setup VSC for DS work.
E.g for if Jupyter doesn't start and this is the first time a user has attempted to run jupyter then:

  • We recommend installing conda (if not installed)
  • We check if conda has been setup correctly
  • We suggest picking a jupyter interpreter from a conda environment...
  • I.e. we walk the user through the process..

Today, we ask user to install jupyter if not found, then later we ask user to install ipykernel..
Basically we have prompts with solutions, but only when users run into an issue.
I think we can improve this experience, rather than letting users stumble around and fix for themselves..

Kind of a Wizard approach, using standard prompts with steps like in Azure where they have Step 1, Step 2,, etc)

We could bring this prompt (that kicks off this workflow), when jupyter doesn't start or kernel fails, or the like.

@rholland
Copy link

I think this is a good idea. I have installed vscode-python on a dozen different computers over the last year, mostly Windows 10. They are all a little different - some Anaconda - some Windows store Python - some python.org Python. I don't do anything special but I may choose different options provided by the install routines. In almost every case "jupyter notebook" works from the command line but the interactive notebook/window in vs code does not. It typically takes 1/2 to 2 hours of googling and messing around to get it to work, and the reasons are always different.

@DonJayamanne
Copy link
Contributor Author

@rholland thanks for your feedback, would it be possible to list some of the issues you encountered and how you fixed them. E.g. you learnt x was not installed (an error message was displayed that clearly indicated this) and you installed it manually (or the extension gave you the ability to install x).
Thanks

@rholland
Copy link

Sure. I will add things over the next week as I get a bit of time. Thanks very much for all of your good work. VSCode-Python is a pleasure to use.

@rholland
Copy link

rholland commented Jul 6, 2020

The recent Jupyter initialization experience is getting better. From my point of view this issue could be closed. Thanks for the good work.

@DonJayamanne DonJayamanne transferred this issue from microsoft/vscode-python Nov 13, 2020
@greazer greazer added feature-request Request for new features or functionality and removed enhancement labels May 4, 2022
@IanMatthewHuff IanMatthewHuff self-assigned this Aug 12, 2022
@IanMatthewHuff IanMatthewHuff removed their assignment Nov 10, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality notebook-getting-started
Projects
None yet
Development

No branches or pull requests

5 participants