The perils of multiple Pythons

Rich Shepard rshepard at
Mon Apr 30 18:24:45 EDT 2018

On Mon, 30 Apr 2018, justin walters wrote:

> With Python 3.5+, venv is a built in module. If using a venv, default to
> using the binary in the venv. That's what I do anyways.

   I'm running Python3-3.6.5 and have a developing application in
~/development/project/. Can I run 'python3 -m venv ~/development/project/'
to install it in a directory with existing modules?


More information about the Python-list mailing list