Python typically uses a special type of file called a Wheel to create a downloadable package that contains Python source code and any additional resources or bundled libraries required for the package. Wheel files replaced the older “egg” file format that Python used for distribution.
Most software libraries for Python are distributed as wheel files, including from the major repositories such as PyPi .
A wheel file itself is built using the same format as the ZIP
file format. Typically, wheel files themselves are built by the setuptools
library, which is not itself part of the core Python language but can be quickly installed as a package using
Finally, a wheel file can include additional information about the software, giving the details such as the version of the software and the developer.
Installing a Wheel File.
Thankfully, installing a Python wheel file is very simple. Most recent versions of the
pip3 tool will handle this automatically via one of two methods.
- We can use
pip3 install <packagename>to find and download the package from PyPi . Most package entries on PyPi give the exact command needed to install them.
- We can install a downloaded wheel file using
pip3 install <file>, where
<file>is the path and name of a wheel file we downloaded manually.
In either case,
pip3 will handle downloading, extracting and installing the Python wheel file on our system so it is ready for us to use in our Python applications.
As we learned in the “Hello Real World” project, we can also list these requirements in a
requirements.txt file to have them automatically installed by
pip3 when we use the
tox command to automate checking and testing our application. In that case, we typically store any manually downloaded wheel files in a folder named
lib inside of our package directory, and then we can add entries to
tox.ini that look like
lib/<filename>.whl to make sure the wheel file is installed properly in the virtual environment as well.