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

Question

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?

Usually you just commit `requirements.txt` and exclude everything else (`env/` typically). — Arount, Sep 18 '17 at 11:42
Do I need `requirements.txt` if I am using Pipenv? the Pipfile should be enough? — Julien Le Coupanec, Sep 18 '17 at 11:59

score 80 · Accepted Answer · edited Jul 07 '21 at 15:23

80

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

edited Jul 07 '21 at 15:23

Al Sweigart

9,509
9
59
85

answered Sep 19 '17 at 14:38

wiesson

5,839
4
36
61

1

Thanks for the explainations – Julien Le Coupanec Sep 19 '17 at 15:00
5

The main maintainer of pipenv also recommends to commit the file (especially for applications): https://github.com/kennethreitz/pipenv/issues/598 – Julien Le Coupanec Sep 19 '17 at 22:13

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

1 Answers1