-
Notifications
You must be signed in to change notification settings - Fork 71
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
Update INSTALL.pipeline #514
base: master
Are you sure you want to change the base?
Conversation
Install instructions to account for new python incompatibility
INSTALL.pipeline
Outdated
echo 'export PATH="$HOME/.pyenv/bin:$PATH"' >> ~/.bashrc | ||
echo 'export "$(pyenv init -)"' >> ~/.bashrc | ||
echo 'eval "$(pyenv virtualenv-init -)"' >> ~/.bashrc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This isn't quite right. Things changed a bit in pyenv in May (pyenv/pyenv#1898). The background is that PATH
modifications belong in ~/.profile
, not ~/.bashrc
, because the latter may be sourced multiple times. pyenv init
does PATH
manipulations as well as other things that need to be in ~/.bashrc
(namely shell integration via a function). But on some systems, ~/.profile
sources ~/.bashrc
when invoked from a Bash shell, which makes things even messier...
Here are all the details: https://github.com/pyenv/pyenv#basic-github-checkout
I've never used the installer/pyenv.run, but I think it prints instructions after installation on how to correctly configure things? Can we just refer to those instead of listing it explicitly here?
Co-authored-by: JustAnotherArchivist <[email protected]>
tcp-closer instructions
Install instructions to account for new python incompatibility