Skip to content

Commit beb9718

Browse files
authored
Update user_guide.rst
1 parent b62076f commit beb9718

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

docs/html/user_guide.rst

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -127,6 +127,10 @@ Logically, a Requirements file is just a list of :ref:`pip install` arguments
127127
placed in a file. Note that you should not rely on the items in the file being
128128
installed by pip in any particular order.
129129

130+
Requirements files can also be served via a URL, e.g.
131+
http://example.com/requirements.txt besides as local files, so that they can
132+
be stored and served in a centralized place.
133+
130134
In practice, there are 4 common uses of Requirements files:
131135

132136
1. Requirements files are used to hold the result from :ref:`pip freeze` for the
@@ -242,16 +246,16 @@ organisation and use that everywhere. If the thing being installed requires
242246
"helloworld" to be installed, your fixed version specified in your constraints
243247
file will be used.
244248

245-
Constraints file can be served via a URL, e.g.
246-
http://example.com/constraints.txt instead of only a local file, so that your
247-
organization can provide constraints files online from a centraliazed place.
248-
249249
Constraints file support was added in pip 7.1. In :ref:`Resolver
250250
changes 2020` we did a fairly comprehensive overhaul, removing several
251251
undocumented and unsupported quirks from the previous implementation,
252252
and stripped constraints files down to being purely a way to specify
253253
global (version) limits for packages.
254254

255+
The same as requirements files, constraints files can be served via a URL, e.g.
256+
http://example.com/constraints.txt, so that your organization can store and
257+
serve them in a centralized place.
258+
255259
.. _`Installing from Wheels`:
256260

257261

0 commit comments

Comments
 (0)