PIP_COMPATIBILITY.md: typo fixes (#2859)

This commit is contained in:
Jelle Zijlstra 2024-04-07 08:34:02 -04:00 committed by GitHub
parent 424d7ab610
commit a217752cac
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions

View File

@ -30,7 +30,7 @@ drawbacks:
target tool the user is expecting to use. target tool the user is expecting to use.
4. It prevents uv from introducing any settings or configuration that don't exist in the target 4. It prevents uv from introducing any settings or configuration that don't exist in the target
tool, since otherwise `pip.conf` (or similar) would no longer be usable with `pip`. tool, since otherwise `pip.conf` (or similar) would no longer be usable with `pip`.
5. It can lead user confusion, since uv would be reading settings that don't actually affect its 5. It can lead to user confusion, since uv would be reading settings that don't actually affect its
behavior, and many users may _not_ expect uv to read configuration files intended for other behavior, and many users may _not_ expect uv to read configuration files intended for other
tools. tools.
@ -107,7 +107,7 @@ the available versions of a given package. However, uv and `pip` differ in how t
packages that exist on multiple indexes. packages that exist on multiple indexes.
For example, imagine that a company publishes an internal version of `requests` on a private index For example, imagine that a company publishes an internal version of `requests` on a private index
(`--extra-index-url`), but also allow installing packages from PyPI by default. In this case, the (`--extra-index-url`), but also allows installing packages from PyPI by default. In this case, the
private `requests` would conflict with the public [`requests`](https://pypi.org/project/requests/) private `requests` would conflict with the public [`requests`](https://pypi.org/project/requests/)
on PyPI. on PyPI.
@ -117,7 +117,7 @@ finds a match. This means that if a package exists on multiple indexes, uv will
candidate versions to those present in the first index that contains the package. candidate versions to those present in the first index that contains the package.
`pip`, meanwhile, will combine the candidate versions from all indexes, and select the best `pip`, meanwhile, will combine the candidate versions from all indexes, and select the best
version from the combined set., though it makes [no guarantees around the order](https://github.com/pypa/pip/issues/5045#issuecomment-369521345) version from the combined set, though it makes [no guarantees around the order](https://github.com/pypa/pip/issues/5045#issuecomment-369521345)
in which it searches indexes, and expects that packages are unique up to name and version, even in which it searches indexes, and expects that packages are unique up to name and version, even
across indexes. across indexes.