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

Option to use existing virtual environments in different locations #22751

Closed
jrmoserbaltimore opened this issue Jan 15, 2024 · 2 comments
Closed
Labels
area-environments Features relating to handling interpreter environments feature-request Request for new features or functionality needs community feedback Awaiting community feedback

Comments

@jrmoserbaltimore
Copy link

#20055 was closed because someone put a path in to go to where "the venvs" are.

I have venvs in various places. Under %APPDATA% for various applications that create their own venvs (e.g. thonny), under %USERPROFILE% where I've manually created venvs, in places in various paths under Documents, and so forth. Pointing to "the folder with venvs" doesn't work because that's several folders scattered all over the place.

We need a feature that allows the use of existing virtual environments, not existing virtual environments but only those in one specific directory. It needs to be like Thonny where you just go to wherever it is and it adds it to the list of virtual environments even if they're in different folders, on different partitions...even on different devices in Thonny's case, but that's a bigger scope than I'm worried about here.

@jrmoserbaltimore jrmoserbaltimore added the feature-request Request for new features or functionality label Jan 15, 2024
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Jan 15, 2024
@anthonykim1 anthonykim1 added needs community feedback Awaiting community feedback area-environments Features relating to handling interpreter environments and removed triage-needed Needs assignment to the proper sub-team labels Jan 16, 2024
Copy link

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

@brettcannon
Copy link
Member

Thank you for submitting your feature request and everyone who considered it! Unfortunately, this issue did not receive enough votes over the allotted time, and so we are closing the issue.

@brettcannon brettcannon closed this as not planned Won't fix, can't repro, duplicate, stale Jun 25, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 26, 2024
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 feature-request Request for new features or functionality needs community feedback Awaiting community feedback
Projects
None yet
Development

No branches or pull requests

3 participants