Add a section for pyenv#581
Merged
Merged
Conversation
Contributor
Thank you for being conscious of this and not doing it anyway. ;) |
sigmavirus24
added a commit
that referenced
this pull request
Oct 3, 2015
Add a section for pyenv Closes #395
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#395 suggests adding a section on pyenv, and is marked as "PR Would be Accepted".
I've added a section on pyenv under
Your Development Environment > Interpreter Tools. I've talked about how it lets different versions be installed side-by-side, how it allows for multiple interpreters, briefly mentioned how it works, and also suggested the use of pyenv-virtualenv which integrates virtualenvs into the pyenv workflow.I haven't included demonstrations of how to use it, because none of the other sections seem to have that.