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.

Sign up for GitHub

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

Jump to bottom

Create a 'blessed' environment that has known modules installed #9055

Closed
rchiodo opened this issue Feb 16, 2022 · 4 comments
Closed

Create a 'blessed' environment that has known modules installed #9055

rchiodo opened this issue Feb 16, 2022 · 4 comments
Assignees
@minsa110
Labels
feature-request Request for new features or functionality notebook-getting-started *out-of-scope Posted issue is not in scope of VS Code

Comments

@rchiodo
Copy link
Contributor

rchiodo commented Feb 16, 2022

We could add this as a default kernel for most environments.

We'd know that it has a bunch of packages that work.

  • Ipykernel
  • Nbconvert
  • Pandas
  • Debugpy
  • IPython
  • numpy
  • matplotlib
@rchiodo rchiodo added the bug Issue identified by VS Code Team member as probable bug label Feb 16, 2022
@DonJayamanne
Copy link
Contributor

I think we should have a yml file so users can create conda environments for these.

@DonJayamanne
Copy link
Contributor

However the more i think about these, we should submit fixes to the dock container definitions & the like.
Else I'm concerned we just end up proliferating different blessed environments.

@rchiodo
Copy link
Contributor Author

rchiodo commented Feb 16, 2022

I think there's a lot of ways to do this. Docker container might be one (feels like nobody would use it though).

I was thinking a venv that we support for say 3 versions of python or something.

@greazer greazer modified the milestones: February 2022, March 2022 Feb 17, 2022
@minsa110
Copy link
Contributor

https://github.com/microsoft/vscode-python-internalbacklog/issues/420

@greazer greazer added enhancement and removed bug Issue identified by VS Code Team member as probable bug labels Mar 4, 2022
@rchiodo rchiodo modified the milestones: March 2022, April 2022 Mar 23, 2022
@rchiodo rchiodo modified the milestones: April 2022, May 2022 Apr 27, 2022
@greazer greazer added feature-request Request for new features or functionality and removed enhancement labels May 4, 2022
@rchiodo rchiodo modified the milestones: May 2022, June 2022 Jun 1, 2022
@greazer greazer removed this from the June 2022 milestone Jun 8, 2022
@IanMatthewHuff IanMatthewHuff mentioned this issue Jul 7, 2022
Closed
@IanMatthewHuff IanMatthewHuff self-assigned this Aug 12, 2022
@IanMatthewHuff IanMatthewHuff removed their assignment Nov 10, 2022
@DonJayamanne DonJayamanne added the *out-of-scope Posted issue is not in scope of VS Code label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@minsa110 minsa110

Labels
feature-request Request for new features or functionality notebook-getting-started *out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@IanMatthewHuff @DonJayamanne @minsa110 @greazer @rchiodo