Hacker News Reader

HNHacker News

Top New Best Ask Show Jobs

Comment by andrewmcwatters | Hacker News Reader

Full thread

andrewmcwatters·

venv, pip, and requirements.txt are just fine.

View on HN

Unless you want reproducible installations on multiple platforms.

cries in CI

No, they're not. Just teaching a beginner what the hell a venv is is a nightmare

I'm about 20 years into coding, and still don't "actually" know what a venv is haha

venv really doesn't seem meaningfully different than jenv or nvm to me.

Also bad. Modern languages have per-prpject dependencies.

I don't mind venv and pip — they may be inconvenient but at least they work.

The requirements.txt however is essentially broken for any project that changes in time. If you don't freeze transitive dependencies versions your builds break with no prior notice. If you do, transitive dependencies stay there forever even when not needed anymore.

pip-tools solves this problem.

I am fortunate enough to not know why you're wrong (having only ever used Python for my own personal projects); but I've seen enough people claim that (in a corporate setting) you are, to be confident that they're right.

Even with your own personal projects it can become a mare. If you like to code interstitial (in those quiet moments between your day job) and hot desk and have a multi platform environment its pain to just use those tool and setup for each new place - I code on Windows (+wsl), MacOS and linux sometimes. I uses github privately to sync everything. Its just me.

Rye is much quick to get started on a machine; install rye+git etc, pull project from git, rye sync. The sync command does all the lifting, installing python version that I set, setting up a venv and installing deps.

Reply on news.ycombinator.com