pip 25.2__tar.gz → 25.3__tar.gz

{pip-25.2 → pip-25.3}/AUTHORS.txt

@@ -24,6 +24,7 @@ albertg
 Alberto Sottile
 Aleks Bunin
 Ales Erjavec
+Alessandro Molina
 Alethea Flowers
 Alex Gaynor
 Alex Grönholm
@@ -37,6 +38,7 @@ Alexandre Conrad
 Alexey Popravka
 Aleš Erjavec
 Alli
+Aman
 Ami Fischman
 Ananya Maiti
 Anatoly Techtonik
@@ -56,6 +58,7 @@ Aniruddha Basak
 Anish Tambe
 Anrs Hu
 Anthony Sottile
+Antoine Lambert
 Antoine Musso
 Anton Ovchinnikov
 Anton Patrushev
@@ -236,6 +239,7 @@ Dimitri Merejkowsky
 Dimitri Papadopoulos
 Dimitri Papadopoulos Orfanos
 Dirk Stolle
+dkjsone
 Dmitry Gladkov
 Dmitry Volodin
 Domen Kožar
@@ -347,6 +351,7 @@ Igor Sobreira
 Ikko Ashimine
 Ilan Schnell
 Illia Volochii
+Ilya Abdolmanafi
 Ilya Baryshev
 Inada Naoki
 Ionel Cristian Mărieș
@@ -482,6 +487,7 @@ luojiebin
 luz.paz
 László Kiss Kollár
 M00nL1ght
+MajorTanya
 Malcolm Smith
 Marc Abramowitz
 Marc Tamlyn
@@ -498,6 +504,7 @@ Martin Pavlasek
 Masaki
 Masklinn
 Matej Stuchlik
+Mateusz Sokół
 Mathew Jennings
 Mathieu Bridon
 Mathieu Kniewallner
@@ -525,6 +532,7 @@ mayeut
 mbaluna
 Md Sujauddin Sekh
 mdebi
+Meet Vasita
 memoselyk
 meowmeowcat
 Michael
@@ -714,6 +722,7 @@ Shivansh-007
 Shixian Sheng
 Shlomi Fish
 Shovan Maity
+Shubham Nagure
 Simeon Visser
 Simon Cross
 Simon Pichugin

{pip-25.2 → pip-25.3}/NEWS.rst

@@ -9,6 +9,70 @@
 
 .. towncrier release notes start
 
+25.3 (2025-10-24)
+=================
+
+Deprecations and Removals
+-------------------------
+
+- Remove support for the legacy ``setup.py develop`` editable method in setuptools
+  editable installs; setuptools >= 64 is now required. (`#11457 <https://github.com/pypa/pip/issues/11457>`_)
+- Remove the deprecated ``--global-option`` and ``--build-option``.
+  ``--config-setting`` is now the only way to pass options to the build backend. (`#11859 <https://github.com/pypa/pip/issues/11859>`_)
+- Deprecate the ``PIP_CONSTRAINT`` environment variable for specifying build
+  constraints.
+
+  Use the ``--build-constraint`` option or the ``PIP_BUILD_CONSTRAINT`` environment variable
+  instead. When build constraints are used, ``PIP_CONSTRAINT`` no longer affects isolated build
+  environments. To enable this behavior without specifying any build constraints, use
+  ``--use-feature=build-constraint``. (`#13534 <https://github.com/pypa/pip/issues/13534>`_)
+- Remove support for non-standard legacy wheel filenames. (`#13581 <https://github.com/pypa/pip/issues/13581>`_)
+- Remove support for the deprecated ``setup.py bdist_wheel`` mechanism. Consequently,
+  ``--use-pep517`` is now always on, and ``--no-use-pep517`` has been removed. (`#6334 <https://github.com/pypa/pip/issues/6334>`_)
+
+Features
+--------
+
+- When :pep:`658` metadata is available, full distribution files are no longer downloaded when using ``pip lock`` or ``pip install --dry-run``. (`#12603 <https://github.com/pypa/pip/issues/12603>`_)
+- Add support for installing an editable requirement written as a Direct URL (``PackageName @ URL``). (`#13495 <https://github.com/pypa/pip/issues/13495>`_)
+- Add support for build constraints via the ``--build-constraint`` option. This
+  allows constraining the versions of packages used during the build process
+  (e.g., setuptools) without affecting the final installation. (`#13534 <https://github.com/pypa/pip/issues/13534>`_)
+- On ``ResolutionImpossible`` errors, include a note about causes with no candidates. (`#13588 <https://github.com/pypa/pip/issues/13588>`_)
+- Building pip itself from source now uses flit-core instead of setuptools.
+  This does not affect how pip installs or builds packages you use. (`#13743 <https://github.com/pypa/pip/issues/13743>`_)
+
+Bug Fixes
+---------
+
+- Handle malformed ``Version`` metadata entries and
+  show a sensible error message instead of crashing. (`#13443 <https://github.com/pypa/pip/issues/13443>`_)
+- Permit spaces between a filepath and extras in an install requirement. (`#13523 <https://github.com/pypa/pip/issues/13523>`_)
+- Ensure the self-check files in the cache have the same permissions as the rest of the cache. (`#13528 <https://github.com/pypa/pip/issues/13528>`_)
+- Avoid concurrency issues and improve performance when caching locally built wheels,
+  especially when the temporary build directory is on a different filesystem than the cache.
+  The wheel directory passed to the build backend is now a temporary subdirectory inside
+  the cache directory. (`#13540 <https://github.com/pypa/pip/issues/13540>`_)
+- Include relevant user-supplied constraints in logs when reporting dependency conflicts. (`#13545 <https://github.com/pypa/pip/issues/13545>`_)
+- Fix a regression in configuration parsing that was turning a single value
+  into a list and thus leading to a validation error. (`#13548 <https://github.com/pypa/pip/issues/13548>`_)
+- For Python versions that do not support :pep:`706`, pip will now raise an installation error for a
+  source distribution when it includes a symlink that points outside the source distribution archive. (`#13550 <https://github.com/pypa/pip/issues/13550>`_)
+- Prevent ``--user`` installs if ``site.ENABLE_USER_SITE`` is set to ``False``. (`#8794 <https://github.com/pypa/pip/issues/8794>`_)
+
+
+Vendored Libraries
+------------------
+
+- Upgrade certifi to 2025.10.5
+- Upgrade msgpack to 1.1.2
+- Upgrade platformdirs to 4.5.0
+- Upgrade requests to 2.32.5
+- Upgrade resolvelib to 1.2.1
+- Upgrade rich to 14.2.0
+- Upgrade tomli to 2.3.0
+- Upgrade truststore to 0.10.4
+
 25.2 (2025-07-30)
 =================
 

{pip-25.2 → pip-25.3}/PKG-INFO

@@ -1,13 +1,11 @@
 Metadata-Version: 2.4
 Name: pip
-Version: 25.2
+Version: 25.3
 Summary: The PyPA recommended tool for installing Python packages.
 Author-email: The pip developers <distutils-sig@python.org>
+Requires-Python: >=3.9
+Description-Content-Type: text/x-rst
 License-Expression: MIT
-Project-URL: Homepage, https://pip.pypa.io/
-Project-URL: Documentation, https://pip.pypa.io
-Project-URL: Source, https://github.com/pypa/pip
-Project-URL: Changelog, https://pip.pypa.io/en/stable/news/
 Classifier: Development Status :: 5 - Production/Stable
 Classifier: Intended Audience :: Developers
 Classifier: Topic :: Software Development :: Build Tools
@@ -22,17 +20,15 @@ Classifier: Programming Language :: Python :: 3.13
 Classifier: Programming Language :: Python :: 3.14
 Classifier: Programming Language :: Python :: Implementation :: CPython
 Classifier: Programming Language :: Python :: Implementation :: PyPy
-Requires-Python: >=3.9
-Description-Content-Type: text/x-rst
 License-File: AUTHORS.txt
 License-File: LICENSE.txt
-License-File: src/pip/_vendor/msgpack/COPYING
 License-File: src/pip/_vendor/cachecontrol/LICENSE.txt
 License-File: src/pip/_vendor/certifi/LICENSE
 License-File: src/pip/_vendor/dependency_groups/LICENSE.txt
 License-File: src/pip/_vendor/distlib/LICENSE.txt
 License-File: src/pip/_vendor/distro/LICENSE
 License-File: src/pip/_vendor/idna/LICENSE.md
+License-File: src/pip/_vendor/msgpack/COPYING
 License-File: src/pip/_vendor/packaging/LICENSE
 License-File: src/pip/_vendor/packaging/LICENSE.APACHE
 License-File: src/pip/_vendor/packaging/LICENSE.BSD
@@ -44,11 +40,13 @@ License-File: src/pip/_vendor/requests/LICENSE
 License-File: src/pip/_vendor/resolvelib/LICENSE
 License-File: src/pip/_vendor/rich/LICENSE
 License-File: src/pip/_vendor/tomli/LICENSE
-License-File: src/pip/_vendor/tomli/LICENSE-HEADER
 License-File: src/pip/_vendor/tomli_w/LICENSE
 License-File: src/pip/_vendor/truststore/LICENSE
 License-File: src/pip/_vendor/urllib3/LICENSE.txt
-Dynamic: license-file
+Project-URL: Changelog, https://pip.pypa.io/en/stable/news/
+Project-URL: Documentation, https://pip.pypa.io
+Project-URL: Homepage, https://pip.pypa.io/
+Project-URL: Source, https://github.com/pypa/pip
 
 pip - The Python Package Installer
 ==================================
@@ -110,3 +108,4 @@ rooms, and mailing lists is expected to follow the `PSF Code of Conduct`_.
 .. _User IRC: https://kiwiirc.com/nextclient/#ircs://irc.libera.chat:+6697/pypa
 .. _Development IRC: https://kiwiirc.com/nextclient/#ircs://irc.libera.chat:+6697/pypa-dev
 .. _PSF Code of Conduct: https://github.com/pypa/.github/blob/main/CODE_OF_CONDUCT.md
+

pip-25.3/build-project/build-requirements.in

@@ -0,0 +1,2 @@
+build
+flit-core

pip-25.3/build-project/build-requirements.txt

@@ -0,0 +1,22 @@
+#
+# This file is autogenerated by pip-compile with Python 3.12
+# by the following command:
+#
+#    pip-compile --allow-unsafe --generate-hashes build-requirements.in
+#
+build==1.3.0 \
+    --hash=sha256:698edd0ea270bde950f53aed21f3a0135672206f3911e0176261a31e0e07b397 \
+    --hash=sha256:7145f0b5061ba90a1500d60bd1b13ca0a8a4cebdd0cc16ed8adf1c0e739f43b4
+    # via -r build-requirements.in
+flit-core==3.12.0 \
+    --hash=sha256:18f63100d6f94385c6ed57a72073443e1a71a4acb4339491615d0f16d6ff01b2 \
+    --hash=sha256:e7a0304069ea895172e3c7bb703292e992c5d1555dd1233ab7b5621b5b69e62c
+    # via -r build-requirements.in
+packaging==25.0 \
+    --hash=sha256:29572ef2b1f17581046b3a2227d5c611fb25ec70ca1ba8554b24b0e69331a484 \
+    --hash=sha256:d443872c98d677bf60f6a1f2f8c1cb748e8fe762d2bf9d3148b5599295b0fc4f
+    # via build
+pyproject-hooks==1.2.0 \
+    --hash=sha256:1e859bd5c40fae9448642dd871adf459e5e2084186e8d2c2a79a824c970da1f8 \
+    --hash=sha256:9e5c6bfa8dcc30091c74b0cf803c81fdd29d94f01992a7707bc97babb1141913
+    # via build

{pip-25.2 → pip-25.3}/docs/html/cli/pip.rst

@@ -77,7 +77,7 @@ when decision is needed.
 .. _`2-build-system-interface`:
 .. rubric:: Build System Interface
 
-This is now covered in :doc:`../reference/build-system/index`.
+This is now covered in :doc:`../reference/build-system`.
 
 .. _`General Options`:
 

{pip-25.2 → pip-25.3}/docs/html/cli/pip_freeze.rst

@@ -23,6 +23,15 @@ Description
 
 .. pip-command-description:: freeze
 
+.. note::
+   By default, ``pip freeze`` omits bootstrap packaging tools so the output
+   focuses on your project’s dependencies. On Python **3.11 and earlier**
+   this excludes ``pip``, ``setuptools``, ``wheel`` and ``distribute``; on
+   Python **3.12 and later** only ``pip`` is excluded. Use ``--all`` to
+   include those packages when you need a complete environment snapshot.
+   ``pip freeze`` reports what is installed; it does **not** compute a
+   lockfile or a solver result.
+
 
 Options
 =======

{pip-25.2 → pip-25.3}/docs/html/cli/pip_install.rst

@@ -66,8 +66,8 @@ for the name and project version (this is in theory slightly less reliable
 than using the ``egg_info`` command, but avoids downloading and processing
 unnecessary numbers of files).
 
-Any URL may use the ``#egg=name`` syntax (see :doc:`../topics/vcs-support`) to
-explicitly state the project name.
+The :ref:`Direct URL requirement syntax <pypug:dependency-specifiers>` can be used
+to explicitly state the project name (see :doc:`../topics/vcs-support`).
 
 Satisfying Requirements
 -----------------------
@@ -255,7 +255,7 @@ This is now covered in :doc:`../topics/local-project-installs`.
 .. _`0-build-system-interface`:
 .. rubric:: Build System Interface
 
-This is now covered in :doc:`../reference/build-system/index`.
+This is now covered in :doc:`../reference/build-system`.
 
 .. _`pip install Options`:
 
@@ -367,21 +367,21 @@ Examples
 
       .. code-block:: shell
 
-         python -m pip install -e 'git+https://git.repo/some_pkg.git#egg=SomePackage'          # from git
-         python -m pip install -e 'hg+https://hg.repo/some_pkg.git#egg=SomePackage'            # from mercurial
-         python -m pip install -e 'svn+svn://svn.repo/some_pkg/trunk/#egg=SomePackage'         # from svn
-         python -m pip install -e 'git+https://git.repo/some_pkg.git@feature#egg=SomePackage'  # from 'feature' branch
-         python -m pip install -e 'git+https://git.repo/some_repo.git#egg=subdir&subdirectory=subdir_path' # install a python package from a repo subdirectory
+         python -m pip install -e 'SomePackage @ git+https://git.repo/some_pkg.git'          # from git
+         python -m pip install -e 'SomePackage @ hg+https://hg.repo/some_pkg.git'            # from mercurial
+         python -m pip install -e 'SomePakcage @ svn+svn://svn.repo/some_pkg/trunk/'         # from svn
+         python -m pip install -e 'SomePackage @ git+https://git.repo/some_pkg.git@feature'  # from 'feature' branch
+         python -m pip install -e 'SomePackage @ git+https://git.repo/some_repo.git#subdirectory=subdir_path' # install a python package from a repo subdirectory
 
    .. tab:: Windows
 
       .. code-block:: shell
 
-         py -m pip install -e "git+https://git.repo/some_pkg.git#egg=SomePackage"          # from git
-         py -m pip install -e "hg+https://hg.repo/some_pkg.git#egg=SomePackage"            # from mercurial
-         py -m pip install -e "svn+svn://svn.repo/some_pkg/trunk/#egg=SomePackage"         # from svn
-         py -m pip install -e "git+https://git.repo/some_pkg.git@feature#egg=SomePackage"  # from 'feature' branch
-         py -m pip install -e "git+https://git.repo/some_repo.git#egg=subdir&subdirectory=subdir_path" # install a python package from a repo subdirectory
+         py -m pip install -e "SomePackage @ git+https://git.repo/some_pkg.git"          # from git
+         py -m pip install -e "SomePackage @ hg+https://hg.repo/some_pkg.git"            # from mercurial
+         py -m pip install -e "SomePackage @ svn+svn://svn.repo/some_pkg/trunk/"         # from svn
+         py -m pip install -e "SomePackage @ git+https://git.repo/some_pkg.git@feature"  # from 'feature' branch
+         py -m pip install -e "SomePackage @ git+https://git.repo/some_repo.git#subdirectory=subdir_path" # install a python package from a repo subdirectory
 
 #. Install a package with extras, i.e., optional dependencies
    (:ref:`specification <pypug:dependency-specifiers>`).
@@ -479,12 +479,11 @@ Examples
 
    .. warning::
 
-       Using this option to search for packages which are not in the main
-       repository (such as private packages) is unsafe, per a security
-       vulnerability called
-       `dependency confusion <https://azure.microsoft.com/en-us/resources/3-ways-to-mitigate-risk-using-private-package-feeds/>`_:
-       an attacker can claim the package on the public repository in a way that
-       will ensure it gets chosen over the private package.
+       Using the ``--extra-index-url`` option to search for packages which are
+       not in the main repository (for example, private packages) is unsafe.
+       This is a class of security issue known as `dependency confusion <https://azure.microsoft.com/en-us/resources/3-ways-to-mitigate-risk-using-private-package-feeds/>`_: an
+       attacker can publish a package with the same name to a public index,
+       which may then be chosen instead of your private package.
 
    .. tab:: Unix/macOS
 

{pip-25.2 → pip-25.3}/docs/html/cli/pip_lock.rst

@@ -35,7 +35,7 @@ Options
 Examples
 ========
 
-#. Emit a ``pylock.toml`` for the the project in the current directory
+#. Emit a ``pylock.toml`` for the project in the current directory
 
    .. tab:: Unix/macOS
 

{pip-25.2 → pip-25.3}/docs/html/cli/pip_wheel.rst

@@ -28,7 +28,7 @@ Description
 .. _`1-build-system-interface`:
 .. rubric:: Build System Interface
 
-This is now covered in :doc:`../reference/build-system/index`.
+This is now covered in :doc:`../reference/build-system`.
 
 Differences to ``build``
 ------------------------

{pip-25.2 → pip-25.3}/docs/html/development/architecture/anatomy.rst

@@ -18,7 +18,6 @@ The ``README``, license, ``pyproject.toml``, and so on are in the top level.
 
 * ``AUTHORS.txt``
 * ``LICENSE.txt``
-* ``MANIFEST.in``
 * ``NEWS.rst``
 * ``pyproject.toml``
 * ``README.rst``
@@ -31,7 +30,6 @@ The ``README``, license, ``pyproject.toml``, and so on are in the top level.
   * ``html/`` *[sources to HTML documentation avail. online]*
   * ``man/`` has man pages the distros can use by running ``man pip``
   * ``pip_sphinxext.py`` *[an extension -- pip-specific plugins to Sphinx that do not apply to other packages]*
-  * ``requirements.txt``
 
 * ``news/`` *[pip stores news fragments… Every time pip makes a user-facing change, a file is added to this directory (usually a short note referring to a GitHub issue) with the right extension & name so it gets included in changelog…. So every release the maintainers will be deleting old files in this directory? Yes - we use the towncrier automation to generate a NEWS file, and auto-delete old stuff. There’s more about this in the contributor documentation!]*
 

pip-25.2/docs/html/reference/build-system/pyproject-toml.md → pip-25.3/docs/html/reference/build-system.md

@@ -1,8 +1,11 @@
-# `pyproject.toml`
+(build-interface)=
 
-```{versionadded} 10.0
+# Build System Interface
 
-```
+When dealing with installable source distributions of a package, pip does not
+directly handle the build process for the package. This responsibility is
+delegated to "build backends" -- also known as "build systems". This means
+that pip needs an interface, to interact with these build backends.
 
 Modern Python packages can contain a `pyproject.toml` file, first introduced in
 {pep}`518` and later expanded in {pep}`517`, {pep}`621` and {pep}`660`.
@@ -96,16 +99,6 @@ For performing editable installs, pip will use {pep}`660`
 `build_wheel_for_editable` hook that has to be provided by the build backend.
 The wheels generated using this mechanism are not cached.
 
-```{admonition} Compatibility fallback
-If this hook is missing on the build backend _and_ there's a `setup.py` file
-in the project, pip will fallback to the legacy setup.py-based editable
-installation.
-
-This is considered a stopgap solution until setuptools adds support for
-{pep}`660`, at which point this functionality will be removed; following pip's
-regular {ref}`deprecation policy <Deprecation Policy>`.
-```
-
 ### Backend Configuration
 
 Build backends have the ability to accept configuration settings, which can
@@ -125,8 +118,7 @@ files.
 ## Build output
 
 It is the responsibility of the build backend to ensure that the output is
-in the correct encoding, as described in {pep}`517`. This likely involves
-dealing with [the same challenges as pip has for legacy builds](build-output).
+in the correct encoding, as described in {pep}`517`.
 
 ## Fallback Behaviour
 
@@ -138,7 +130,8 @@ https://setuptools.pypa.io/en/stable/userguide/quickstart.html#basic-use).
 ```
 
 If a project does not have a `pyproject.toml` file containing a `build-system`
-section, it will be assumed to have the following backend settings:
+section, and contains a `setup.py` it will be assumed to have the following
+backend settings:
 
 ```toml
 [build-system]
@@ -164,14 +157,36 @@ passed.
 
 ## Historical notes
 
+```{versionadded} 10.0
+
+```
+
 As this feature was incrementally rolled out, there have been various notable
 changes and improvements in it.
 
-- setuptools 40.8.0 is the first version of setuptools that offers a
-  {pep}`517` backend that closely mimics directly executing `setup.py`.
-- Prior to pip 18.0, pip only supports installing build requirements from
-  wheels, and does not support the use of environment markers and extras (only
-  version specifiers are respected).
-- Prior to pip 18.1, build dependencies using `.pth` files are not properly
-  supported; as a result namespace packages do not work under Python 3.2 and
-  earlier.
+Setuptools 40.8.0 is the first version of setuptools that offers a
+{pep}`517` backend that closely mimics directly executing `setup.py`.
+
+```{versionadded} 18.0
+Prior to pip 18.0, pip only supports installing build requirements from
+wheels, and does not support the use of environment markers and extras (only
+version specifiers are respected).
+```
+
+```{versionadded} 18.1
+Prior to pip 18.1, build dependencies using `.pth` files are not properly
+supported; as a result namespace packages do not work under Python 3.2 and
+earlier.
+```
+
+```{versionchanged} 23.1
+The legacy interface where pip could invoke `setup.py install`
+in some circumstances was removed,
+in favor of the fallback behavior described above.
+```
+
+```{versionchanged} 25.3
+The legacy interface where pip could invoke `setup.py build_wheel` or
+`setup.py develop` in some circumstances was removed,
+in favor of the fallback behavior described above.
+```

{pip-25.2 → pip-25.3}/docs/html/reference/index.md

@@ -6,7 +6,7 @@ interoperability standards that pip utilises/implements.
 ```{toctree}
 :titlesonly:
 
-build-system/index
+build-system
 requirement-specifiers
 requirements-file-format
 installation-report

{pip-25.2 → pip-25.3}/docs/html/reference/requirements-file-format.md

@@ -109,7 +109,6 @@ and two {ref}`--find-links <install_--find-links>` locations:
 
 The options which can be applied to individual requirements are:
 
-- {ref}`--global-option <install_--global-option>`
 - {ref}`--config-settings <install_--config-settings>`
 - `--hash` (for {ref}`Hash-checking mode`)
 
@@ -150,30 +149,3 @@ You can now store sensitive data (tokens, keys, etc.) in environment variables
 and only specify the variable name for your requirements, letting pip lookup
 the value at runtime. This approach aligns with the commonly used
 [12-factor configuration pattern](https://12factor.net/config).
-
-
-## Influencing the build system
-
-```{danger}
-This disables the use of wheels (cached or otherwise). This could mean that builds will be slower, less deterministic, less reliable and may not behave correctly upon installation.
-
-This mechanism is only preserved for backwards compatibility and should be considered deprecated. A future release of pip may drop these options.
-```
-
-The `--global-option` option is used to pass options to `setup.py`.
-
-```{attention}
-These options are highly coupled with how pip invokes setuptools using the {doc}`../reference/build-system/setup-py` build system interface. It is not compatible with newer {doc}`../reference/build-system/pyproject-toml` build system interface.
-
-This is will not work with other build-backends or newer setup.cfg-only projects.
-```
-
-If you have a declaration like:
-
-    FooProject >= 1.2 --global-option="--no-user-cfg"
-
-The above translates roughly into running FooProject's `setup.py` script as:
-
-    python setup.py --no-user-cfg install
-
-Note that the only way of giving more than one option to `setup.py` is through multiple `--global-option` options.

{pip-25.2 → pip-25.3}/docs/html/topics/dependency-resolution.md

@@ -165,6 +165,9 @@ will avoid performing dependency resolution during deployment.
 
 ## Dealing with dependency conflicts
 
+This section uses hypothetical packages (`package_coffee`, `package_tea`, and
+`package_water`) to explain how pip resolves conflicts.
+
 This section provides practical suggestions to pip users who encounter
 a `ResolutionImpossible` error, where pip cannot install their specified
 packages due to conflicting dependencies.
@@ -194,6 +197,11 @@ because they each depend on different versions of the same package
 - ``package_tea`` version ``4.3.0`` depends on version ``2.3.1`` of
   ``package_water``
 
+Note: `package_coffee`, `package_tea`, and `package_water` are hypothetical
+packages used only to illustrate dependency conflicts. They are not real
+projects you can install.
+
+
 Sometimes these messages are straightforward to read, because they use
 commonly understood comparison operators to specify the required version
 (e.g. `<` or `>`).
@@ -252,10 +260,10 @@ the same version of `package_water`, you might consider:
 
 In the second case, pip will automatically find a version of both
 `package_coffee` and `package_tea` that depend on the same version of
-`package_water`, installing:
+`package_water`, for example:
 
 - `package_coffee 0.44.1`, which depends on `package_water 2.6.1`
-- `package_tea 4.4.3` which _also_ depends on `package_water 2.6.1`
+- `package_tea 4.4.3`, which also depends on `package_water 2.6.1`
 
 If you want to prioritize one package over another, you can add version
 specifiers to _only_ the more important package:

{pip-25.2 → pip-25.3}/docs/html/topics/local-project-installs.md

@@ -37,17 +37,6 @@ With an editable install, you only need to perform a re-installation if you chan
 It is possible to see behaviour differences between regular installs vs editable installs. These differences depend on the build-backend, and you should check the build-backend documentation for the details. In case you distribute the project as a "distribution package", users will see the behaviour of regular installs -- thus, it is important to ensure that regular installs work correctly.
 ```
 
-```{note}
-This is functionally the same as [setuptools' develop mode], and that's precisely the mechanism used for setuptools-based projects.
-
-There are two advantages over using `setup.py develop` directly:
-
-- This works with non-setuptools build-backends as well.
-- The ".egg-info" directory is created relative to the project path, when using pip. This is generally a better location than setuptools, which dumps it in the current working directory.
-```
-
-[setuptools' develop mode]: https://setuptools.readthedocs.io/en/latest/userguide/development_mode.html
-
 ## Build artifacts
 
 ```{versionchanged} 21.3

{pip-25.2 → pip-25.3}/docs/html/topics/repeatable-installs.md

@@ -90,10 +90,3 @@ across machines.
 Hash-checking mode can also be used along with this method (since this uses a
 requirements file as well), to ensure that future archives are built with
 identical packages.
-
-```{warning}
-Beware of the `setup_requires` keyword arg in {file}`setup.py`. The (rare)
-packages that use it will cause those dependencies to be downloaded by
-setuptools directly, skipping pip's protections. If you need to use such a
-package, see {ref}`Controlling setup_requires <controlling-setup_requires>`.
-```

{pip-25.2 → pip-25.3}/docs/html/topics/secure-installs.md

@@ -77,10 +77,6 @@ Other hash algorithms that have guaranteed support from `hashlib` are also suppo
 
 Hash-checking mode also works with {ref}`pip download` and {ref}`pip wheel`. See {doc}`../topics/repeatable-installs` for a comparison of hash-checking mode with other repeatability strategies.
 
-```{warning}
-Beware of the `setup_requires` keyword arg in {file}`setup.py`. The (rare) packages that use it will cause those dependencies to be downloaded by setuptools directly, skipping pip's hash-checking. If you need to use such a package, see {ref}`controlling setup_requires <controlling-setup_requires>`.
-```
-
 ## Do not use setuptools directly
 
 Be careful not to nullify all your security work by installing your actual project by using setuptools' deprecated interfaces directly: for example, by calling `python setup.py install`, `python setup.py develop`, or `easy_install`.