1PIP-WHEEL(1)                          pip                         PIP-WHEEL(1)
2
3
4

NAME

6       pip-wheel - description of pip wheel command
7

DESCRIPTION

9       Build Wheel archives for your requirements and dependencies.
10
11       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
15       'pip  wheel'  uses  the  build  system  interface  as  described  here:
16       https://pip.pypa.io/en/stable/reference/build-system/
17
18

USAGE

20          python -m pip wheel [options] <requirement specifier> ...
21          python -m pip wheel [options] -r <requirements file> ...
22          python -m pip wheel [options] [-e] <vcs project url> ...
23          python -m pip wheel [options] [-e] <local project path> ...
24          python -m pip wheel [options] <archive url/path> ...
25

OPTIONS

27       -w, --wheel-dir <dir>
28              Build wheels into <dir>, where the default is the current  work‐
29              ing directory.
30
31       --no-binary <format_control>
32              Do  not use binary packages. Can be supplied multiple times, and
33              each time adds to the existing value. Accepts either ":all:"  to
34              disable  all  binary packages, ":none:" to empty the set (notice
35              the colons), or one or more package names  with  commas  between
36              them  (no colons). Note that some packages are tricky to compile
37              and may fail to install when this option is used on them.
38
39       --only-binary <format_control>
40              Do not use source packages. Can be supplied multiple times,  and
41              each  time adds to the existing value. Accepts either ":all:" to
42              disable all source packages, ":none:" to empty the set,  or  one
43              or more package names with commas between them. Packages without
44              binary distributions will fail to install when  this  option  is
45              used on them.
46
47       --prefer-binary
48              Prefer older binary packages over newer source packages.
49
50       --no-build-isolation
51              Disable  isolation  when  building a modern source distribution.
52              Build dependencies specified by PEP  518  must  be  already  in‐
53              stalled if this option is used.
54
55       --use-pep517
56              Use   PEP   517   for   building   source   distributions   (use
57              --no-use-pep517 to force legacy behaviour).
58
59       --check-build-dependencies
60              Check the build dependencies when PEP517 is used.
61
62       -c, --constraint <file>
63              Constrain versions using the given constraints file. This option
64              can be used multiple times.
65
66       -e, --editable <path/url>
67              Install  a  project  in  editable mode (i.e. setuptools "develop
68              mode") from a local project path or a VCS url.
69
70       -r, --requirement <file>
71              Install from the given requirements file.  This  option  can  be
72              used multiple times.
73
74       --src <dir>
75              Directory  to check out editable projects into. The default in a
76              virtualenv is "<venv path>/src". The default for global installs
77              is "<current dir>/src".
78
79       --ignore-requires-python
80              Ignore the Requires-Python information.
81
82       --no-deps
83              Don't install package dependencies.
84
85       --progress-bar <progress_bar>
86              Specify  whether  the progress bar should be used [on, off] (de‐
87              fault: on)
88
89       --no-verify
90              Don't verify if built wheel is valid.
91
92       -C, --config-settings <settings>
93              Configuration settings to be passed to the PEP 517  build  back‐
94              end.  Settings  take  the  form  KEY=VALUE.  Use multiple --con‐
95              fig-settings options to pass multiple keys to the backend.
96
97       --build-option <options>
98              Extra arguments to be supplied to 'setup.py bdist_wheel'.
99
100       --global-option <options>
101              Extra global options to be supplied to the setup.py call  before
102              the install or bdist_wheel command.
103
104       --pre  Include  pre-release  and  development versions. By default, pip
105              only finds stable versions.
106
107       --require-hashes
108              Require a hash to check each requirement against, for repeatable
109              installs.  This option is implied when any package in a require‐
110              ments file has a --hash option.
111
112       --no-clean
113              Don't clean up build directories.
114
115

AUTHOR

117       pip developers
118
120       The pip developers
121
122
123
124
12523.2                             Aug 04, 2023                     PIP-WHEEL(1)
Impressum