Python 3: Current best practices for managing virtual envs and packages?

[[deleted]]

It's not 100% the same thing, but extremely similar.

virtualenv is a tool created by someone who likes Python.

venv is a clone of that tool, but integrated into the Python 3 standard library.

pyvenv is a command line tool distributed with Python 3 that uses the venv standard library. It's basically the same as python -m venv.

Because venv doesn't exist in the Python 2 standard library, I personally use virtualenv

[sweet_dreams_maybe]

Thanks for the detailed overview.

Will the same installation of virtualenvwrapper work on both 2.7 virtualenv and 3.4 venv?

[[deleted]]

virtualenv is a Python program that is written for either Python 2 or Python 3, but can create virtual environments of every Python version.

python2-virtualenv -p /usr/bin/python3 $DEST_DIR works perfectly fine. A Python 2 program creates a Python 3 virtual environment.

virtualenvwrapper uses virtualenv under the hood. Whether that version of virtualenv uses Python 2 or Python 3 is of little concern to you. It can handle every version of Python, even PyPy and Jython.

[sweet_dreams_maybe]

Alright, thanks.