kennethreitz/pipenv
1
0
Fork 0
mirror of https://github.com/kennethreitz/pipenv.git synced 2026-06-05 22:50:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Expand a bit on sync vs ignore-pipfile

Browse Source 
- expanded a bit on the distinction between `sync` and `ignore-pipfile`
- fixed a merge conflict resolution I did that erased some changes in master
This commit is contained in:
Dan Ryan
2018-08-31 00:16:09 -04:00
committed by GitHub
parent d1d6b87b05
commit 7f602daf98
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/advanced.rst
+5 -4
View File
@@ -113,12 +113,13 @@ You can enforce that your ``Pipfile.lock`` is up to date using the ``--deploy``
This will fail a build if the ``Pipfile.lock`` is out–of–date, instead of generating a new one.
Or you can install packages exactly as specified in ``Pipfile.lock`` using the sync command::
Or you can install packages exactly as specified in ``Pipfile.lock`` using the ``sync`` command::
$ pipenv sync
Note: ``pipenv install --ignore-pipfile`` is nearly equivalent to ``pipenv sync``, but you should use ``pipenv sync`` instead.
``--ignore-pipfile`` may be removed in a future version.
.. note::
``pipenv install --ignore-pipfile`` is nearly equivalent to ``pipenv sync``, but you ``pipenv sync`` will *never* attempt to re-lock your dependencies as it is considered an atomic operation. ``pipenv install`` by default does attempt to re-lock unless using the ``--deploy`` flag.
Deploying System Dependencies
/////////////////////////////
@@ -127,7 +128,7 @@ You can tell Pipenv to install a Pipfile's contents into its parent system with
$ pipenv install --system
This is useful for Docker containers, and deployment infrastructure (e.g. Heroku does this).
This is useful for managing the system Python, and deployment infrastructure (e.g. Heroku does this).
☤ Pipenv and Other Python Distributions
---------------------------------------