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

Respect .python-version as suggested by pyenv (and pyenv-virtualenv) #15473

Closed
muuvmuuv opened this issue Feb 21, 2021 · 4 comments
Closed

Respect .python-version as suggested by pyenv (and pyenv-virtualenv) #15473

muuvmuuv opened this issue Feb 21, 2021 · 4 comments
Labels
area-environments Features relating to handling interpreter environments feature-request Request for new features or functionality needs PR Ready to be worked on

Comments

@muuvmuuv
Copy link

There are several issues about not finding the correct python interpreter, but none about the fact that a simple .python-version file holds the version or virtualenv name that this extension can simply parse and select the interpreter based on it.

@muuvmuuv muuvmuuv added triage-needed Needs assignment to the proper sub-team feature-request Request for new features or functionality labels Feb 21, 2021
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Feb 22, 2021
@karthiknadig karthiknadig added area-environments Features relating to handling interpreter environments triage-needed Needs assignment to the proper sub-team and removed triage-needed Needs assignment to the proper sub-team labels Feb 22, 2021
@karthiknadig
Copy link
Member

Thank you for the suggestion! We have marked this issue as "needs decision" to make sure we have a conversation about your idea. We plan to leave this feature request open for at least a month to see how many 👍 votes the opening comment gets to help us make our decision.

@bersbersbers
Copy link

I'm not sure if issuing pyenv local || pyenv global may be more robust, though. @muuvmuuv, I have this problem a lot, could you list some of these other issues here?

@tigerhawkvok
Copy link

On Windows at least, you could get around this by allowing the default interpreter to be the pyenv shim, but it's not allowed to be selected as the default Python.

@github-actions github-actions bot removed the needs PR label Aug 9, 2022
@karrtikr karrtikr added the needs PR Ready to be worked on label Aug 9, 2022
@anthonykim1
Copy link

Looks like a dup of #1167 This should've been resolved with #23094, I believe. Are folks still experiencing this issue? I'm going to close the issue but please let us know if you are still suffering from this, I can reopen this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-environments Features relating to handling interpreter environments feature-request Request for new features or functionality needs PR Ready to be worked on
Projects
None yet
Development

No branches or pull requests

7 participants