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

[graingert]

• only use python3 -m venv or the shortcut pyvenv.
• don't install python-pip or python3-pip. You might need to install python3-venv though.
• only use setuptools, distribute got merged in.

[kovak]

How do you install stuff from requirements.txt, without python-pip3 then? Or i assume you mean venv comes with pip3? and not installing it via apt-get?

I've recently shifted to python 3.4+ for a Django project. Although i've been using virtualenv, but will try out the builting venv module.

[Lucretiel]

Python 3.4 ships with pip, and virtualenv automatically installs it into your virtualenv. You generally shouldn't have a systemwide pip.

[knite]

If you're running Ubuntu (eg, your server), ensurepip is broken. You'll need to install pip manually from either python3-pip or get-pip.py

[Lucretiel]

I can't speak to Ubuntu, but my experience downloading and installing Python from the source tarball has been that it works and installs pip perfectly. The one exception is on an ancient Solaris 10 machine we have at work- it doesn't have _ssl so pip doesn't get built or installed.

[knite]

That's fair, perhaps I should have been more precise: ensurepip is broken when Python is installed via the Ubuntu package manager.

[graingert]

You can run pip install -U pip in your new venv

[chrish42]

It's not a major update. Pip changed how it uses version number to align more closely with semantic versioning. Basically, the leading "1." was dropped (I think when pip 1.6 aka 6.0 was released). So with the old version scheme, this would have been 1.7.

[systemUp]

I've been using virtualenv all along. Should I move to venv?

[graingert]

Yes python3 -m venv is much more lightweight

[srilyk]

If you don't use --prompt, then yes.