mirror of https://github.com/pypa/pip
Styling changes
This commit is contained in:
parent
6813caadab
commit
5a608324fb
|
@ -22,9 +22,9 @@ Policy
|
|||
Rationale
|
||||
---------
|
||||
|
||||
Historically pip has not had any dependencies except for setuptools itself,
|
||||
Historically pip has not had any dependencies except for ``setuptools`` itself,
|
||||
choosing instead to implement any functionality it needed to prevent needing
|
||||
a dependency. However, starting with pip 1.5 we began to replace code that was
|
||||
a dependency. However, starting with pip 1.5, we began to replace code that was
|
||||
implemented inside of pip with reusable libraries from PyPI. This brought the
|
||||
typical benefits of reusing libraries instead of reinventing the wheel like
|
||||
higher quality and more battle tested code, centralization of bug fixes
|
||||
|
@ -43,7 +43,7 @@ way (via ``install_requires``) for pip. These issues are:
|
|||
|
||||
* **Making other libraries uninstallable.** One of pip's current dependencies is
|
||||
the ``requests`` library, for which pip requires a fairly recent version to run.
|
||||
If pip dependended on ``requests`` in the traditional manner, then we'd either
|
||||
If pip depended on ``requests`` in the traditional manner, then we'd either
|
||||
have to maintain compatibility with every ``requests`` version that has ever
|
||||
existed (and ever will), OR allow pip to render certain versions of ``requests``
|
||||
uninstallable. (The second issue, although technically true for any Python
|
||||
|
|
Loading…
Reference in New Issue