mirror of
https://github.com/getpelican/pelican.git
synced 2025-10-15 20:28:56 +02:00
Remove references to easy_install in documentation
This commit is contained in:
parent
1461197826
commit
d19854f4dc
2 changed files with 3 additions and 4 deletions
|
|
@ -79,9 +79,8 @@ automatically installed without any action on your part:
|
||||||
Upgrading
|
Upgrading
|
||||||
---------
|
---------
|
||||||
|
|
||||||
If you installed a stable Pelican release via ``pip`` or ``easy_install`` and
|
If you installed a stable Pelican release via ``pip`` and wish to upgrade to
|
||||||
wish to upgrade to the latest stable release, you can do so by adding
|
the latest stable release, you can do so by adding ``--upgrade``::
|
||||||
``--upgrade`` to the relevant command. For pip, that would be::
|
|
||||||
|
|
||||||
pip install --upgrade pelican
|
pip install --upgrade pelican
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -46,7 +46,7 @@ the ``output`` dir generated by Pelican to a repository's ``gh-pages`` branch
|
||||||
on GitHub.
|
on GitHub.
|
||||||
|
|
||||||
The excellent `ghp-import <https://github.com/davisp/ghp-import>`_, which can
|
The excellent `ghp-import <https://github.com/davisp/ghp-import>`_, which can
|
||||||
be installed with ``easy_install`` or ``pip``, makes this process really easy.
|
be installed with ``pip``, makes this process really easy.
|
||||||
|
|
||||||
For example, if the source of your Pelican site is contained in a GitHub
|
For example, if the source of your Pelican site is contained in a GitHub
|
||||||
repository, and if you want to publish that Pelican site in the form of Project
|
repository, and if you want to publish that Pelican site in the form of Project
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue