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

NAME

6       pip-download - description of pip download command
7

DESCRIPTION

9       Download packages from:
10
11       · PyPI (and other indexes) using requirement specifiers.
12
13       · VCS project urls.
14
15       · Local project directories.
16
17       · Local or remote source archives.
18
19       pip  also supports downloading from "requirements files", which provide
20       an easy way to specify a whole environment to be downloaded.
21
22

USAGE

24          pip download [options] <requirement specifier> [package-index-options] ...
25          pip download [options] -r <requirements file> [package-index-options] ...
26          pip download [options] <vcs project url> ...
27          pip download [options] <local project path> ...
28          pip download [options] <archive url/path> ...
29

OPTIONS

31       -c, --constraint <file>
32              Constrain versions using the given constraints file. This option
33              can be used multiple times.
34
35       -r, --requirement <file>
36              Install  from  the  given  requirements file. This option can be
37              used multiple times.
38
39       -b, --build <dir>
40              (DEPRECATED) Directory to unpack packages  into  and  build  in.
41              Note  that  an  initial  build  still takes place in a temporary
42              directory. The location of temporary  directories  can  be  con‐
43              trolled by setting the TMPDIR environment variable (TEMP on Win‐
44              dows) appropriately. When  passed,  build  directories  are  not
45              cleaned in case of failures.
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
93              installed 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       -d, --dest <dir>
100              Download packages into <dir>.
101
102       --platform <platform>
103              Only  use  wheels  compatible  with  <platform>. Defaults to the
104              platform of the running system.
105
106       --python-version <python_version>
107              The  Python  interpreter  version   to   use   for   wheel   and
108              "Requires-Python"  compatibility  checks.  Defaults to a version
109              derived from the running interpreter. The version can be  speci‐
110              fied  using  up  to  three  dot-separated integers (e.g. "3" for
111              3.0.0, "3.7" for 3.7.0, or "3.7.3"). A major-minor  version  can
112              also be given as a string without dots (e.g. "37" for 3.7.0).
113
114       --implementation <implementation>
115              Only use wheels compatible with Python implementation <implemen‐
116              tation>, e.g. 'pp', 'jy', 'cp',  or 'ip'. If not specified, then
117              the  current  interpreter  implementation  is used.  Use 'py' to
118              force implementation-agnostic wheels.
119
120       --abi <abi>
121              Only  use  wheels  compatible  with  Python  abi   <abi>,   e.g.
122              'pypy_41'.   If  not specified, then the current interpreter abi
123              tag is used.  Generally you will need to  specify  --implementa‐
124              tion, --platform, and --python-version when using this option.
125
126       --no-clean
127              Don't clean up build directories.
128
129

AUTHOR

131       pip developers
132

134       2008-2020, PyPA
135
136
137
138
13920.2                            August 05, 2020                PIP-DOWNLOAD(1)
Impressum