pyenv-virtualenv
pyenv-virtualenv copied to clipboard
`_pyenv_virtualenv_hook` still in $PROMPT_COMMAND after uninstall
I was using pyenv+pyenv-virtualenv installed via brew on macOS. I uninstalled it and removed virtualenv-init from my bashrc, but it still gets added to PROMPT_COMMAND which now makes every new terminal fail with -bash: _pyenv_virtualenv_hook: command not found
.
Too many issues will kill our team's development velocity, drastically. Make sure you have checked all steps below.
Prerequisite
- [x] Make sure your problem is not listed in the common build problems.
- [x] Make sure no duplicated issue has already been reported in the pyenv-virtualenv issues. You should look in closed issues, too.
- [x] Make sure you are not asking us to help solving your specific issue.
- GitHub issues is opened mainly for development purposes. If you want to ask someone to help solving your problem, go to some community site like Gitter, StackOverflow, etc.
- [x] Make sure your problem is not derived from packaging (e.g. Homebrew).
- Please refer to the package documentation for the installation issues, etc.
- [x] Make sure your problem is not derived from other plugins.
- This repository is maintaining the
pyenv-virtualenv
plugin only. Please refrain from reporting issues of other plugins here.
- This repository is maintaining the
Description
- [x] Platform information (e.g. Ubuntu Linux 20.04): macOS
- [x] OS architecture (e.g. amd64): arm64
- [x] pyenv version: 2.4.3
- [x] pyenv-virtualenv version: 1.2.3
- [x] Python version: 3.12.2
- [ ] virtualenv version (if installed):
- [ ] Please attach the debug log of a faulty Pyenv invocation as a gist
- If the problem happens in a Pyenv invocation, you can turn on debug logging by setting
PYENV_DEBUG=1
, e.g.env PYENV_DEBUG=1 pyenv install -v 3.6.4
- If the problem happens outside of a Pyenv invocation, get the debug log like this:
# for Bash export PS4='+(${BASH_SOURCE}:${LINENO}): ${FUNCNAME[0]:+${FUNCNAME[0]}(): }' # for Zsh export PS4='+(%x:%I): %N(%i): ' set -x <reproduce the problem> set +x
- If the problem happens in a Pyenv invocation, you can turn on debug logging by setting