micro-blog-[ish]

91 readers

4 users here now

A place to say what you have to say, without requiring any context, theme, arguments, or ceremony. Be civil.

founded 6 months ago

MODERATORS

xia@lemmy.sdf.org

TIL how broken the python package manager is (lemmy.sdf.org)

submitted 1 month ago by xia@lemmy.sdf.org to c/microblogish@lemmy.sdf.org

5 comments fedilink hide all child comments

So maybe I'm spoiled by linux package managers, where you tell it to "upgrade" and things continue to work... to me that is just a natural expectation.

Well, it seems the python package manager (pip) will happily upgrade all your project's required dependencies, but not your optional dependencies... yet the old (incompatible) version is still visible at runtime.

Consequently, it seems to be an excepted norm in the python world that things may break after a "pip upgrade", at least on a single tool.

How do python devs put up with this? Apparently there are a bunch of hacks scattered across countless projects to test at runtime for incompatible deps, even though they have already dutifully specified the compatible version in the dependencies list.

What a mess.

you are viewing a single comment's thread
view the rest of the comments

[–] assaultpotato@sh.itjust.works 2 points 1 month ago (1 children)

pip is insufficient, this is known.

Use uv or pipenv, they're faster, better, and more clear when things go wrong.

[–] dis_honestfamiliar@lemmy.sdf.org 1 points 3 weeks ago

You are saying that I can use uv yo install packages.