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

python pip pipenv
Julien Le Coupanec picture Julien Le Coupanec · Sep 18, 2017 · Viewed 8.1k times · Source

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

For PHP, most people recommend to commit composer.lock file.

Do we have to do the same for Python?

Answer

wiesson picture wiesson · Sep 19, 2017

Short - Yes!

The lock file tells pipenv exactly which version of each dependency needs to be installed. You will have consistency across all machines.

// update: Same question on github

Related questions

Pipenv: Command Not Found

I'm new to Python development and attempting to use pipenv. I ran the command pip install pipenv, which ran successfully: ... Successfully built pipenv pathlib shutilwhich pythonz-bd virtualenv-clone Installing collected packages: virtualenv, pathlib, shutilwhich, backports.shutil-get-terminal-size, pythonz-bd, virtualenv-clone, pew, first, six, …

Read More
How to install dependencies from a copied pipfile inside a virtual environment?

The problem originates when I start by cloning a git project that uses pipenv, so it has a Pipfile + Pipfile.lock. I want to use a virtual environment with the project so I run pipenv shell. I now have a …

Read More
Windows reports error when trying to install package using pipenv

I installed pipenv by following the instructions here. From the Windows command prompt I ran pip install --user pipenv which returned the message Successfully installed pipenv-5.3.3 Now I want to install the requests package using pipenv, so I ran pipenv …

Read More