From 51c3c8b6004b65256e06e7cfecf524db6efa15b0 Mon Sep 17 00:00:00 2001 From: Gabi Nagy Date: Thu, 13 Sep 2018 17:02:56 +0300 Subject: [PATCH] Fix `pipenv install --dev` description By default, `pipenv install` will install packages based on the list in `Pipfile`, not `Pipfile.lock`. `pipenv install --dev` is no exception. I've tested this using pipenv 2018.7.1 with different package versions in `Pipfile` and `Pipfile.lock`. After `pipenv install`, the versions in `Pipfile` were the ones actually installed. --- docs/basics.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/basics.rst b/docs/basics.rst index 559f7570..5d41249f 100644 --- a/docs/basics.rst +++ b/docs/basics.rst @@ -287,7 +287,7 @@ The user can provide these additional parameters: folder is encoded into a "slug value" and appended to ensure the virtualenv name is unique. - - ``--dev`` — Install both ``develop`` and ``default`` packages from ``Pipfile.lock``. + - ``--dev`` — Install both ``develop`` and ``default`` packages from ``Pipfile``. - ``--system`` — Use the system ``pip`` command rather than the one from your virtualenv. - ``--ignore-pipfile`` — Ignore the ``Pipfile`` and install from the ``Pipfile.lock``. - ``--skip-lock`` — Ignore the ``Pipfile.lock`` and install from the ``Pipfile``. In addition, do not write out a ``Pipfile.lock`` reflecting changes to the ``Pipfile``.