summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTzu-ping Chung <uranusjr@gmail.com>2023-04-14 05:12:09 +0800
committerGitHub <noreply@github.com>2023-04-14 05:12:09 +0800
commit5d3f24dac1c461ec095d879aa4984ae09916be88 (patch)
tree7bf9c8401330ac5c3fe1288434ffa233bb449966
parent74133f810cb2507ebac3fcaa73098f0370b3aab5 (diff)
parentd914ffa92700e938ebc5327683605606dfdfacf1 (diff)
downloadpip-5d3f24dac1c461ec095d879aa4984ae09916be88.tar.gz
Merge pull request #11954 from honnix/patch-1
-rw-r--r--docs/html/user_guide.rst8
-rw-r--r--news/11954.doc.rst1
2 files changed, 9 insertions, 0 deletions
diff --git a/docs/html/user_guide.rst b/docs/html/user_guide.rst
index 966b200f4..9a6f2901c 100644
--- a/docs/html/user_guide.rst
+++ b/docs/html/user_guide.rst
@@ -127,6 +127,10 @@ Logically, a Requirements file is just a list of :ref:`pip install` arguments
placed in a file. Note that you should not rely on the items in the file being
installed by pip in any particular order.
+Requirements files can also be served via a URL, e.g.
+http://example.com/requirements.txt besides as local files, so that they can
+be stored and served in a centralized place.
+
In practice, there are 4 common uses of Requirements files:
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,
and stripped constraints files down to being purely a way to specify
global (version) limits for packages.
+Same as requirements files, constraints files can also be served via a URL,
+e.g. http://example.com/constraints.txt, so that your organization can store and
+serve them in a centralized place.
+
.. _`Installing from Wheels`:
diff --git a/news/11954.doc.rst b/news/11954.doc.rst
new file mode 100644
index 000000000..946b4057f
--- /dev/null
+++ b/news/11954.doc.rst
@@ -0,0 +1 @@
+Make it clear that requirements/constraints file can be a URL