Skip to content

Commit 5d3f24d

Browse files
authored
Merge pull request #11954 from honnix/patch-1
2 parents 74133f8 + d914ffa commit 5d3f24d

File tree

2 files changed

+9
-0
lines changed

2 files changed

+9
-0
lines changed

docs/html/user_guide.rst

Lines changed: 8 additions & 0 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
@@ -248,6 +252,10 @@ undocumented and unsupported quirks from the previous implementation,
248252
and stripped constraints files down to being purely a way to specify
249253
global (version) limits for packages.
250254

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

253261

news/11954.doc.rst

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
Make it clear that requirements/constraints file can be a URL

0 commit comments

Comments
 (0)