# Build a directory of wheels for pyramid and all its dependencies
pip wheel --wheel-dir=/tmp/wheelhouse pyramid
# Install from cached wheels
pip install --use-wheel --no-index --find-links=/tmp/wheelhouse pyramid
# Install from cached wheels remotely
pip install --use-wheel --no-index --find-links=https://wheelhouse.example.com/ pyramid
$ python wheel-0.21.0-py2.py3-none-any.whl/wheel -h
The `bdist_wheel` command automatically determines the correct tags to use for
-the generated wheel.
These are based on the Python interpreter used to
+the generated wheel. These are based on the Python interpreter used to
generate the wheel and whether the project contains C extension code or not.
While this is usually correct for C code, it can be too conservative for pure
Python code. The bdist_wheel command therefore supports two flags that can be
--universal Specifies that a pure-python wheel is "universal"
(i.e., it works on any version of Python). This
equates to the tag "py2.py3".
- --python-tag XXX Specifies the preci
de python version tag to use for
+ --python-tag XXX Specifies the precie python version tag to use for
Neither of these two flags have any effect when used on a project that includes
was released (the first version containing the `with` statement), wheels for a
project that used the `with` statement would typically use `--python-tag py25`.
-Typically, projects would not specify
python tags on the command line, but
+Typically, projects would not specify ython tags on the command line, but
would use `setup.cfg` to set them as a project default::
$ pip install wheel[tool]
# Generate a signing key (only once)
- $ export WHEEL_TOOL=/path/to/wheel
+ $ export WHEEL_TOOL=/path/to/wheel
$ python setup.py bdist_wheel
Signing is done in a subprocess because it is not convenient for the