3 ms·
For me it was the promise to be able to maintain my dependencies up to date and avoid manually handling configuration files. Working in a team it is often usef
by tutuca 8y ago
For me it was the promise to be able to maintain my dependencies up to date and avoid manually handling configuration files.
Working in a team it is often useful to have your versions "pinned" down so you have a reproducible environment regardless of upstream backwards compatibility policy (just to name one example).
The Pipfile + Pifile.lock combo seemed right for the task.
Creating virtualenv was a nice plus.
- Twirrim 8y agoWhat was wrong with requirements.txt? We heavily use virtualenvs and just pin package versions there. I've yet to see it fail.
- guitarbill 8y agoupdating requirements.txt is a pain, and also development dependencies vs normal ones usually results in two requirements files. lock files are a good way to do this, so borrowing from npm et al isn't a bad move. (for what it's worth, i use pipenv and rather like it.)