Hacker News Reader

Comment by magnio | Hacker News Reader

Whatever project solves Python dependency management deserves to get a Nobel in Economics for saving humanity billion of hours per year.

View on HN

Usually I simply use pip and poetry. Haven't run into an issue in a long time. Privately I use Guix often, when it has the required packages. I find the dependency management mostly to be already solved. Perhaps I am not riding along the edge enough, to see things broken.

Pip has gone down the shithole with its preaching about venvs. It's my computer. I'll install to site-packages if I damn well want to.

What I usually do is make a venv using pip, then use that venv to install poetry in it, because I don't want to clutter my system with outdated poetry package. Then use Poetry to install packages inside the venv. So the pip part is merely for bootstrapping.

You shouldn't have to launch a sub-shell to run a script interpreter. That is exemplary of how nobody in the Python leadership can fix their perpetual packaging f-ups of the last two decades and are now just sticking their collective heads in the sand.

Just invoke the python interpreter from its venv path. You don't need the sub-shell.

Poetry does a lot of good stuff: lock file, dev dependencies (and other customizable groups), easy to use virtual env, dependencies pulled directly from git.

I do not recommend pip in serious projects, as it lacks the above. Here's things that I've seen:

- add dependencies and not save them in the requirements file - forget to activate cenv and install packages globally - different package versions across deployments due to absence of lock file - main dependencies mixed with dev dependencies

Reply on news.ycombinator.com