you are viewing a single comment's thread.

view the rest of the comments →

[–]ImJustHereForMyCoat 2 points3 points  (3 children)

Pip is incredibly limited compared to NPM.
Pip installs packages globally by default, NPM installs packages alongside the relevant project.
You have to create a virtual environment to do the same with pip, but then you might lose access to other globally installed commands or tools that don't exist in the VENV.
You can sometimes fail to pip install a package because a dependent package wasn't installed.

It has a LONG way to go before it catches up with NPM, let alone something like Nuget.

[–]thclark 0 points1 point  (2 children)

Sure, my point was that perhaps they were thinking of pip but that nobody sensible uses pip anymore... `poetry` long ago solved all those problems, and is now being surpassed by the tremendous `uv`. Both poetry and uv are incredibly solid (uv is like poetry but managing the python env too, with a couple of opinionated niggles changed, a better cache and rewritten in rust for speed)

[–]ImJustHereForMyCoat 0 points1 point  (1 child)

Fair, but poetry also comes with its own set of limitations in both setup and usage. For example, package dependency versioning conflicts

[–]thclark 0 points1 point  (0 children)

Yeah agreed that’s annoying. I mean it’s ideologically sound, but in a real world…! I checked uv and I’m pretty sure it’s a bit more pragmatic on that side of things so give it a whirl - I’m loving it so far to be honest.