Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

git - Should Pipfile.lock be committed to version control?

See original GitHub issue

When two developers are working on a projet with different operating systems, the Pipfile.lock is different (especially the part inside host-environment-markers).

For Composer, most people recommend to commit composer.lock. Do we have to do the same for Pipenv?

Issue Analytics

State:
Created 6 years ago
Reactions:24
Comments:26 (14 by maintainers)

Top GitHub Comments

111reactions

kennethreitzcommented, Feb 28, 2018

because we are special snowflakes.

70reactions

kennethreitzcommented, Sep 19, 2017

i recommend it.

Top Results From Across the Web

gitignore for Python and Django projects - Toptal

... then you probably don't need or want to include staticfiles/ # in your Git repository. ... it is recommended to include Pipfile.lock...

How is the Pipfile.lock distributed? Is it intended to be checked ...

Yes, source control. Installing the project would cause it to be built from the lock file (assuming the Pipefile hasn't changed). This will...

Basic Usage of Pipenv - Python Packaging Authority

Generally, keep both Pipfile and Pipfile.lock in version control. Do not keep Pipfile.lock in version control if multiple versions of Python are being ......

pipenv Documentation - Read the Docs

lock - Regenerate Pipfile.lock and updates the dependencies inside it. ... You can install packages with pipenv from git and other version control...

Best practices in development

pipenv is currently the recommended tool for dependency management but "consider ... Pipfile.lock which pins dependencies, this means deterministic builds ...