Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What was wrong with requirements.txt? We heavily use virtualenvs and just pin package versions there. I've yet to see it fail.


updating 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.)




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: