If you’re familiar with Python packaging and installation, and just want to know what tools are currently recommended, then here it is.
Installation Tool Recommendations¶
- Use pip to install Python packages from PyPI.   Depending how pip is installed, you may need to also install wheel to get the benefit of wheel caching. 
- Use virtualenv, or pyvenv to isolate application specific dependencies from a shared Python installation. 
- If you’re looking for management of fully integrated cross-platform software stacks, consider buildout (primarily focused on the web development community) or Hashdist, or conda (both primarily focused on the scientific community).
Packaging Tool Recommendations¶
- Use setuptools to define projects and create Source Distributions.  
- Use the
bdist_wheelsetuptools extension available from the wheel project to create wheels. This is especially beneficial, if your project contains binary extensions. 
- Use twine for uploading distributions to PyPI.
|||There are some cases where you might choose to use |
|||The acceptance of PEP 453 means that pip will be available by default in most installations of Python 3.4 or later. See the rationale section from PEP 453 as for why pip was chosen.|
|||get-pip.py and virtualenv install wheel, whereas ensurepip and pyvenv do not currently. Also, the common “python-pip” package that’s found in various linux distros, does not depend on “python-wheel” currently.|
|||Beginning with Python 3.4, |
Although you can use pure
Even for projects that do choose to use
|||distribute (a fork of setuptools) was merged back into setuptools in June 2013, thereby making setuptools the default choice for packaging.|
|||PyPI currently only allows uploading Windows and Mac OS X wheels, and they should be compatible with the binary installers provided for download from python.org. Enhancements will have to be made to the wheel compatibility tagging scheme before linux wheels will be allowed.|