2 ms·
> we had tons of small Pipenv projects and one pain was that a few were Python 3.5 and a few others were Python 3.6 Isn't pipenv supposed to take care of that?
by yorwba 8y ago
> we had tons of small Pipenv projects and one pain was that a few were Python 3.5 and a few others were Python 3.6
Isn't pipenv supposed to take care of that? You pipenv run the tool and it's automatically executed in the right virtual environment.
- leksak 8y agoYou can't set it up without the Python binary you want already being on the machine which may be a hassle if you are chasing "latest" and you have machines in your ecosystem that run old stuff, for instance, Jenkins nodes.
- thijsvandien 8y agoYou'd have to combine it with pyenv to allow for multiple interpreters and automatic switching between them.