1PIP-WHEEL(1) pip PIP-WHEEL(1)
2
6 pip-wheel - description of pip wheel command
7
9 Build Wheel archives for your requirements and dependencies.
10 Wheel is a built-package format, and offers the advantage of not recom‐
12 piling your software during every install. For more details, see the
13 wheel docs: https://wheel.readthedocs.io/en/latest/
14 Requirements: setuptools>=0.8, and wheel.
16 'pip wheel' uses the bdist_wheel setuptools extension from the wheel
18 package to build individual wheels.
19
22 pip wheel [options] <requirement specifier> ...
23 pip wheel [options] -r <requirements file> ...
24 pip wheel [options] [-e] <vcs project url> ...
25 pip wheel [options] [-e] <local project path> ...
26 pip wheel [options] <archive url/path> ...
27
29 -w, --wheel-dir <dir>
30 Build wheels into <dir>, where the default is the current work‐
31 ing directory.
32 --no-binary <format_control>
34 Do not use binary packages. Can be supplied multiple times, and
35 each time adds to the existing value. Accepts either :all: to
36 disable all binary packages, :none: to empty the set, or one or
37 more package names with commas between them (no colons). Note
38 that some packages are tricky to compile and may fail to install
39 when this option is used on them.
40 --only-binary <format_control>
42 Do not use source packages. Can be supplied multiple times, and
43 each time adds to the existing value. Accepts either :all: to
44 disable all source packages, :none: to empty the set, or one or
45 more package names with commas between them. Packages without
46 binary distributions will fail to install when this option is
47 used on them.
48 --prefer-binary
50 Prefer older binary packages over newer source packages.
51 --build-option <options>
53 Extra arguments to be supplied to 'setup.py bdist_wheel'.
54 --no-build-isolation
56 Disable isolation when building a modern source distribution.
57 Build dependencies specified by PEP 518 must be already
58 installed if this option is used.
59 --use-pep517
61 Use PEP 517 for building source distributions (use
62 --no-use-pep517 to force legacy behaviour).
63 -c, --constraint <file>
65 Constrain versions using the given constraints file. This option
66 can be used multiple times.
67 -e, --editable <path/url>
69 Install a project in editable mode (i.e. setuptools "develop
70 mode") from a local project path or a VCS url.
71 -r, --requirement <file>
73 Install from the given requirements file. This option can be
74 used multiple times.
75 --src <dir>
77 Directory to check out editable projects into. The default in a
78 virtualenv is "<venv path>/src". The default for global installs
79 is "<current dir>/src".
80 --ignore-requires-python
82 Ignore the Requires-Python information.
83 --no-deps
85 Don't install package dependencies.
86 -b, --build <dir>
88 Directory to unpack packages into and build in. Note that an
89 initial build still takes place in a temporary directory. The
90 location of temporary directories can be controlled by setting
91 the TMPDIR environment variable (TEMP on Windows) appropriately.
92 When passed, build directories are not cleaned in case of fail‐
93 ures.
94 --progress-bar <progress_bar>
96 Specify type of progress to be displayed
97 [off|on|ascii|pretty|emoji] (default: on)
98 --global-option <options>
100 Extra global options to be supplied to the setup.py call before
101 the 'bdist_wheel' command.
102 --pre Include pre-release and development versions. By default, pip
104 only finds stable versions.
105 --no-clean
107 Don't clean up build directories.
108 --require-hashes
110 Require a hash to check each requirement against, for repeatable
111 installs. This option is implied when any package in a require‐
112 ments file has a --hash option.
113
116 pip developers
117
119 2008-2020, PyPA
12019.3 April 10, 2020 PIP-WHEEL(1)