Apart from the fact that pipenv supports pyenv to install missing Python versions (#981), I think it should be cool if pyenv automatically calls pipenv shell if there's a Pipfile (or activates its environment).
The handling of the paths and the shell is not a responsibility for pipenv, so I think pyenv should do it.
Sorry if I'm misunderstanding, but this responsibility seems completely different than what pyenv currently does.
If you want some commands to run automatically or conveniently in your shell, then wouldn't an alias be better, or a tool like direnv to automatically invoke and set environment variables?
I mean, pyenv already loads the python virtualenv when changing directory. As pipenv is now the recommended way to go, shouldn't it load its virtualenv when changing directory as well?
Ah, okay. The pyenv-virtualenv plugin is actually what does virtualenv auto-loading. You could propose this over there?
Most helpful comment
Ah, okay. The
pyenv-virtualenvplugin is actually what does virtualenv auto-loading. You could propose this over there?