McSinyx/pip
1
1
Fork 0
mirror of https://github.com/pypa/pip synced 2023-12-13 21:30:23 +01:00
Code Issues Releases Activity

docs: fix some typos

Browse source
This commit is contained in:
Xavier Fernandez 2016-02-07 00:11:45 +01:00
parent cb483f6c35
commit 4e586d3297
2 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/reference/pip_install.rst
View file

@ -229,7 +229,7 @@ Some examples:
SomeProject[foo, bar]
SomeProject~=1.4.2
Since version 6.0, pip also supports specifers containing `environment markers
Since version 6.0, pip also supports specifiers containing `environment markers
<https://www.python.org/dev/peps/pep-0426/#environment-markers>`_ like so:
::
@ -586,7 +586,7 @@ cache flushes. Compilation of C code adds further nondeterminism, as many
compilers include random-seeded values in their output. However, wheels fetched
from index servers are the same every time. They land in pip's HTTP cache, not
its wheel cache, and are used normally in hash-checking mode. The only downside
of having the the wheel cache disabled is thus extra build time for sdists, and
of having the wheel cache disabled is thus extra build time for sdists, and
this can be solved by making sure pre-built wheels are available from the index
server.

4
docs/user_guide.rst
View file

@ -86,7 +86,7 @@ In practice, there are 4 common uses of Requirements files:
4. Requirements files are used to override a dependency with a local patch that
lives in version control. For example, suppose a dependency,
`SomeDependency` from PyPI has a bug, and you can't wait for an upstream fix.
You could clone/copy the src, make the fix, and place it in vcs with the tag
You could clone/copy the src, make the fix, and place it in VCS with the tag
`sometag`. You'd reference it in your requirements file with a line like so:
::
@ -483,7 +483,7 @@ E.g. supposing:
* `SomePackage-2.0` and `AnotherPackage-2.0` are the latest versions available on PyPI.
Running ``pip install --upgrade SomePackage`` would upgrade `SomePackage` *and*
`AnotherPackage` despite `AnotherPackage` already being satisifed.
`AnotherPackage` despite `AnotherPackage` already being satisfied.
pip doesn't currently have an option to do an "only if needed" recursive
upgrade, but you can achieve it using these 2 steps::