Skip to content

List of (or types of) environments that can be activated by vscode and unit tests #1527

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
Closed
15 of 30 tasks
DonJayamanne opened this issue Apr 27, 2018 · 5 comments
Closed
15 of 30 tasks

List of (or types of) environments that can be activated by vscode and unit tests #1527

DonJayamanne opened this issue Apr 27, 2018 · 5 comments
Labels
area-environments Features relating to handling interpreter environments debt Covers everything internal: CI, testing, refactoring of the codebase, etc. meta Issue that is tracking an overall project needs PR Ready to be worked on

Comments

@DonJayamanne
Copy link

DonJayamanne commented Apr 27, 2018 •
edited
Loading

Goal of this issue:

  • List different types of python environments (or tools that create python environments)
  • For each of the above ensure we have tests for:
    • Activation of environment in terminal
    • Environment listed in interpreter list
    • Environment is identified correctly
    • Display name is formatted correctly

Also refer to #1351

  1. pipenv
  • Documented?
  • Have unit tests to activate terminal
  • Have unit tests to ensure these are listed in interpreter list
  • Have unit tests to ensure these are identified accordingly
  • Have unit tests to ensure the display names are as expected
  • Does the display name indicate this is a pipenv environment?
  1. pyenv
  • Documented?
  • Have unit tests to activate terminal
  • Have unit tests to ensure these are listed in interpreter list
  • Have unit tests to ensure these are identified accordingly
  • Have unit tests to ensure the display names are as expected
  • Does the display name indicate this is a pyenv environment?
  1. conda
  • Documented?
  • Have unit tests to activate terminal
  • Have unit tests to ensure these are listed in interpreter list
  • Have unit tests to ensure these are identified accordingly
  • Have unit tests to ensure the display names are as expected
  • Does the display name indicate this is a conda environment?
  1. virtualenv
  • Documented?
  • Have unit tests to activate terminal
  • Have unit tests to ensure these are listed in interpreter list
  • Have unit tests to ensure these are identified accordingly
  • Have unit tests to ensure the display names are as expected
  • Does the display name indicate this is a virtualenv environment?
  1. venv
  • Documented?
  • Have unit tests to activate terminal
  • Have unit tests to ensure these are listed in interpreter list
  • Have unit tests to ensure these are identified accordingly
  • Have unit tests to ensure the display names are as expected
  • Does the display name indicate this is a venv environment?
  1. what else

What else?
@DonJayamanne DonJayamanne self-assigned this Apr 27, 2018
@DonJayamanne DonJayamanne added this to the April 2018 milestone Apr 27, 2018
@brettcannon
Copy link
Member

pyenv isn't a type of environment.

@DonJayamanne DonJayamanne changed the title List all types of environments that can be activated by vscode today List all types of tools used to create environments that can be activated by vscode today Apr 27, 2018
@DonJayamanne
Copy link
Author

pyenv isn't a type of environment.

Agreed, poor wording. I'm interested in environments that are created by different tools that are supported by VSC.

@DonJayamanne DonJayamanne changed the title List all types of tools used to create environments that can be activated by vscode today List tools used to create environments that can be activated by vscode today and ensure we have tests Apr 27, 2018
@DonJayamanne DonJayamanne changed the title List tools used to create environments that can be activated by vscode today and ensure we have tests Environments that can be activated by vscode and tests Apr 28, 2018
@brettcannon brettcannon modified the milestones: April 2018, May 2018 May 2, 2018
@DonJayamanne DonJayamanne changed the title Environments that can be activated by vscode and tests List of (or types of) environments that can be activated by vscode and unit tests May 21, 2018
@DonJayamanne DonJayamanne modified the milestones: May 2018, June 2018 May 23, 2018
@brettcannon brettcannon removed this from the June 2018 milestone Jun 4, 2018
@brettcannon brettcannon added meta Issue that is tracking an overall project feature-interpreter debt Covers everything internal: CI, testing, refactoring of the codebase, etc. and removed feature-* labels Sep 19, 2018
@DonJayamanne DonJayamanne removed their assignment Oct 10, 2018
@ringods

This comment has been minimized.

Sign in to view
@brettcannon

This comment has been minimized.

Sign in to view
@microsoft microsoft locked and limited conversation to collaborators Dec 11, 2018
@gramster gramster added area-environments Features relating to handling interpreter environments and removed feature-interpreter labels Oct 10, 2019
@karrtikr karrtikr added the needs PR Ready to be worked on label Aug 9, 2022
@karrtikr
Copy link

Closing as outdated.

@karrtikr karrtikr closed this as not planned Won't fix, can't repro, duplicate, stale Dec 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-environments Features relating to handling interpreter environments debt Covers everything internal: CI, testing, refactoring of the codebase, etc. meta Issue that is tracking an overall project needs PR Ready to be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@brettcannon @ringods @DonJayamanne @gramster @karrtikr