> How do you handle packages?

The same way you handle them with bash?

Install them?

What are we talking about here?

I think it is the fact that python packaging has been problematic for some time. setuptools/easy_install, pip/pipx, poetry, conda, uv all promise they will be the thing that "fixes" it

▲

bigstrat2003 2 hours ago | parent | next [-]

Eh. Python packaging is just fine. Set up a venv, install with pip, done. I think that the difficulty of installing Python packages is wildly overblown on this site.

	▲	bdangubic an hour ago \| parent [-]
		not “AI Bubble” overblown but close

▲

paulddraper a day ago | parent | prev [-]

What does Bash use for its packaging?

Use that.

▲

bccdee a day ago | parent [-]

Ok tbh bash uses the system package manager to install command-line utilities, and using the system package manager for python packages HAS been tried, and the parallel use of system packaging and independent package managers is part of why python package distribution is such a mess.

▲

skydhash 10 hours ago | parent [-]

Why using independent package managers alongside the system one? I think the introduction of non system packagers is what brought us the whole mess we are in. Most system packagers allows for custom repositories.

	▲	bccdee 3 hours ago \| parent [-]
		Because the system package repository doesn't package everything & isn't always up to date. And if you introduce other repos to fix this, then you have an ecosystem with multiple instances of the same package distributed at different versions in different repositories, and God help you if you need multiple versions of one package, or if you need a different version of Python entirely. Nix could do it, but not anything else. No—system python is for the system's scripts, and user projects should have their dependencies sandboxed in a virtual environment. That's the only model that really works.