From 3f13e8dfd3daacb64755d21f92b48e25d6f8fd82 Mon Sep 17 00:00:00 2001 From: Ben Kraft Date: Wed, 25 Apr 2018 11:43:04 -0700 Subject: [PATCH] Mention --keep-outdated in docs for importing When importing from requirements.txt, it may be useful to keep the versions of packages you have for the moment, while unpinning them for the future. This is already supported via `--keep-outdated`; this commit adds a mention to the docs. Fixes #908. --- docs/basics.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/basics.rst b/docs/basics.rst index 78ac66c1..b563de62 100644 --- a/docs/basics.rst +++ b/docs/basics.rst @@ -172,9 +172,10 @@ pipenv will automatically import the contents of this file and create a ``Pipfil You can also specify ``$ pipenv install -r path/to/requirements.txt`` to import a requirements file. -Note, that when importing a requirements file, they often have version numbers pinned, which you likely won't want -in your ``Pipfile``, so you'll have to manually update your ``Pipfile`` afterwards to reflect this. - +If your requirements file has version numbers pinned, you'll likely want to edit the new ``Pipfile`` +to remove those, and let ``pipenv`` keep track of pinning. If you want to keep the pinned versions +in your ``Pipfile.lock`` for now, run ``pipenv lock --keep-outdated``. Make sure to +`upgrade <#initialization>`_ soon! .. _specifying_versions: