The perils of multiple Pythons

Chris Angelico rosuav at
Mon Apr 30 17:22:13 EDT 2018

On Tue, May 1, 2018 at 7:16 AM, Tim Chase <python.list at> wrote:
> On 2018-05-01 06:40, Chris Angelico wrote:
>>>> >>
>>> I feel like this problem is pretty handily solved by virtual
>>> environments. Also, if a single project requires all of this,
>>> perhaps Python isn't the best choice for the project.
>> Some of it is definitely solved by venvs. But which Python binary do
>> you use?
> Pretty sure that all venvs I've used know their corresponding binary.
> But...

Right. It's locked in when you create it. But you still have to pick.

>> And is venv installed? Do you need to install virtualenv
>> first? How do you...
> Is it virtualenv?  Or are you using virtualenvwrapper which, last I
> checked doesn't work in ksh (OpenBSD's default shell) without jumping
> through hoops and getting external ksh-specific files?  Or are you
> using pipenv?  Or `python -m venv`?  So many different flavors. :-(

Exactly! Personally, I don't use any of them except "python3 -m venv",
but I also have some custom bash scripting to make the activation and
deactivation happen automatically.


More information about the Python-list mailing list