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

If there is only one python in the system we should always select it #21348

Closed
karthiknadig opened this issue May 31, 2023 · 4 comments
Closed
Assignees
Labels
area-environments Features relating to handling interpreter environments feature-request Request for new features or functionality triage-needed Needs assignment to the proper sub-team

Comments

@karthiknadig
Copy link
Member

Caveat: As long as the version is something we can support.

@karthiknadig karthiknadig added feature-request Request for new features or functionality area-environments Features relating to handling interpreter environments labels May 31, 2023
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label May 31, 2023
@karthiknadig karthiknadig added needs spike Label for issues that need investigation before they can be worked on. and removed triage-needed Needs assignment to the proper sub-team labels Jun 1, 2023
@karrtikr
Copy link

I can verify that we ideally should always select it based on the current design. Can you add more context to the issue, was it created based on #21256?

@karrtikr karrtikr added triage-needed Needs assignment to the proper sub-team info-needed Issue requires more information from poster and removed needs spike Label for issues that need investigation before they can be worked on. labels Jul 10, 2023
@github-actions
Copy link

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

Happy Coding!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 13, 2023
@karthiknadig
Copy link
Member Author

I can verify that we ideally should always select it based on the current design. Can you add more context to the issue, was it created based on #21256?

Yes

@karthiknadig karthiknadig reopened this Aug 13, 2023
@github-actions github-actions bot removed the info-needed Issue requires more information from poster label Aug 13, 2023
@karrtikr
Copy link

Closing in favor of #21256, will reopen based on the discussion there if needed. FWIW I think this is already being done.

@karrtikr karrtikr closed this as Won't fix, can't repro, duplicate, stale Aug 15, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 15, 2023
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 triage-needed Needs assignment to the proper sub-team
Projects
None yet
Development

No branches or pull requests

2 participants