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

Include <PYENV> in [python-setup].interpreter_search_paths default (Cherry-pick of #10998) #11008

Merged
merged 1 commit into from Oct 21, 2020

Conversation

Eric-Arellano
Copy link
Contributor

[ci skip-rust]
[ci skip-build-wheels]

pantsbuild#10998)

Pyenv interpreters are often very likely to work (compared to some system Pythons), so it's sensible to include in the default.

If the user does not use Pyenv, the `<PYENV>` value will simply no-op. We keep `<PATH>` in the default so that it's more likely Pants works Out Of The Box for new users.
 
[ci skip-rust]
[ci skip-build-wheels]
Copy link
Contributor Author

@Eric-Arellano Eric-Arellano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cherry-pick with no modifications.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 0.0% when pulling 4370bdc on Eric-Arellano:cp-pyenv into 734ffa9 on pantsbuild:2.0.x.

@Eric-Arellano Eric-Arellano merged commit 209d3b8 into pantsbuild:2.0.x Oct 21, 2020
@Eric-Arellano Eric-Arellano deleted the cp-pyenv branch October 21, 2020 20:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants