Include a fix for pyenv with poetry shell in documentation #678
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.
Please see #497, #571, #172, and possibly #198 for related issues.
In the case described by @itsthejoker here: #497 (comment)
a proposed solution is to have
fish
execute a script to fix $PATH after pyenv has initialized. I believe a better solution is to guard pyenv for $POETRY_ACTIVE. This PR includes documentation for this fix, as I suspect many people are hitting this roadblock.I am not able to vouch that this fix works (or is needed) on any shells other than
fish
, but I would assume before merging you might want to include documentation for those shells.Hopefully this is helpful!