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

Allow for "Select at project/folder level" when selecting interpreter #24327

Closed
jimisola opened this issue Oct 23, 2024 · 2 comments
Closed

Allow for "Select at project/folder level" when selecting interpreter #24327

jimisola opened this issue Oct 23, 2024 · 2 comments
Labels
feature-request Request for new features or functionality needs community feedback Awaiting community feedback

Comments

@jimisola
Copy link

jimisola commented Oct 23, 2024

Relates to: #23827

The current "Select at workspace level" when selecting interpreter is good but if you have many projects/folder in your workspace then the list of environments is everything but easy to pick from (see attachment). Perhaps grouping on project/folder would be a good start.

Image
Image

Suggestion would be:

  • Select at workspace level
  • Select at project level
  • Select at project level for current file

For me personally, I always have to use the "Select at option". How is it used by others? Perhaps it should be at the top?

@jimisola jimisola added the feature-request Request for new features or functionality label Oct 23, 2024
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Oct 23, 2024
@karthiknadig karthiknadig added needs community feedback Awaiting community feedback and removed triage-needed Needs assignment to the proper sub-team labels Oct 23, 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.

@eleanorjboyd
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. PRs are welcome so you can create a PR that fixes this if you are passionate about getting this feature across the finish line. Thanks!

@eleanorjboyd eleanorjboyd closed this as not planned Won't fix, can't repro, duplicate, stale Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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