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

NAME

6       pip-download - description of pip download command
7
8       IMPORTANT:
9          Did this article help?
10
11          We  are  currently doing research to improve pip's documentation and
12          would love your feedback.  Please email us and let us know  why  you
13          came  to this page and what on it helped you and what did not.    (‐
14          Read more about this research)
15

DESCRIPTION

17       Download packages from:
18
19       • PyPI (and other indexes) using requirement specifiers.
20
21       • VCS project urls.
22
23       • Local project directories.
24
25       • Local or remote source archives.
26
27       pip also supports downloading from "requirements files", which  provide
28       an easy way to specify a whole environment to be downloaded.
29
30

USAGE

32          python -m pip download [options] <requirement specifier> [package-index-options] ...
33          python -m pip download [options] -r <requirements file> [package-index-options] ...
34          python -m pip download [options] <vcs project url> ...
35          python -m pip download [options] <local project path> ...
36          python -m pip download [options] <archive url/path> ...
37

OPTIONS

39       -c, --constraint <file>
40              Constrain versions using the given constraints file. This option
41              can be used multiple times.
42
43       -r, --requirement <file>
44              Install from the given requirements file.  This  option  can  be
45              used multiple times.
46
47       --no-deps
48              Don't install package dependencies.
49
50       --global-option <options>
51              Extra  global options to be supplied to the setup.py call before
52              the install command.
53
54       --no-binary <format_control>
55              Do not use binary packages. Can be supplied multiple times,  and
56              each  time adds to the existing value. Accepts either ":all:" to
57              disable all binary packages, ":none:" to empty the  set  (notice
58              the  colons),  or  one or more package names with commas between
59              them (no colons). Note that some packages are tricky to  compile
60              and may fail to install when this option is used on them.
61
62       --only-binary <format_control>
63              Do  not use source packages. Can be supplied multiple times, and
64              each time adds to the existing value. Accepts either ":all:"  to
65              disable  all  source packages, ":none:" to empty the set, or one
66              or more package names with commas between them. Packages without
67              binary  distributions  will  fail to install when this option is
68              used on them.
69
70       --prefer-binary
71              Prefer older binary packages over newer source packages.
72
73       --src <dir>
74              Directory to check out editable projects into. The default in  a
75              virtualenv is "<venv path>/src". The default for global installs
76              is "<current dir>/src".
77
78       --pre  Include pre-release and development versions.  By  default,  pip
79              only finds stable versions.
80
81       --require-hashes
82              Require a hash to check each requirement against, for repeatable
83              installs. This option is implied when any package in a  require‐
84              ments file has a --hash option.
85
86       --progress-bar <progress_bar>
87              Specify     type     of     progress     to     be     displayed
88              [off|on|ascii|pretty|emoji] (default: on)
89
90       --no-build-isolation
91              Disable isolation when building a  modern  source  distribution.
92              Build  dependencies  specified  by  PEP  518 must be already in‐
93              stalled if this option is used.
94
95       --use-pep517
96              Use   PEP   517   for   building   source   distributions   (use
97              --no-use-pep517 to force legacy behaviour).
98
99       --ignore-requires-python
100              Ignore the Requires-Python information.
101
102       -d, --dest <dir>
103              Download packages into <dir>.
104
105       --platform <platform>
106              Only  use  wheels  compatible  with  <platform>. Defaults to the
107              platform of the running system. Use this option  multiple  times
108              to  specify  multiple  platforms  supported by the target inter‐
109              preter.
110
111       --python-version <python_version>
112              The Python  interpreter  version  to  use  for  wheel  and  "Re‐
113              quires-Python"  compatibility  checks. Defaults to a version de‐
114              rived from the running interpreter. The version can be specified
115              using  up  to  three dot-separated integers (e.g. "3" for 3.0.0,
116              "3.7" for 3.7.0, or "3.7.3"). A major-minor version can also  be
117              given as a string without dots (e.g. "37" for 3.7.0).
118
119       --implementation <implementation>
120              Only use wheels compatible with Python implementation <implemen‐
121              tation>, e.g. 'pp', 'jy', 'cp',  or 'ip'. If not specified, then
122              the  current  interpreter  implementation  is used.  Use 'py' to
123              force implementation-agnostic wheels.
124
125       --abi <abi>
126              Only  use  wheels  compatible  with  Python  abi   <abi>,   e.g.
127              'pypy_41'.  If  not  specified, then the current interpreter abi
128              tag is used. Use this option multiple times to specify  multiple
129              abis  supported  by  the  target interpreter. Generally you will
130              need to specify --implementation, --platform, and  --python-ver‐
131              sion when using this option.
132
133       --no-clean
134              Don't clean up build directories.
135
136
137       IMPORTANT:
138          Did this article help?
139
140          We  are  currently doing research to improve pip's documentation and
141          would love your feedback.  Please email us and let us know:
142
143          1. What problem were you trying to solve when you came to this page?
144
145          2. What content was useful?
146
147          3. What content was not useful?
148

AUTHOR

150       pip developers
151
153       2008-2021, PyPA
154
155
156
157
15821.0                             May 17, 2021                  PIP-DOWNLOAD(1)
Impressum