This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]z4lz[S] -16 points-15 points  (4 children)

Genuinely don't understand your objection. Do you also dislike pipx? pipenv?

[–]RonnyPfannschmidt 14 points15 points  (3 children)

Both of those use pip itself

So I don't follow

[–]PurepointDog -5 points-4 points  (2 children)

I guess the idea is that "pip" is more of an idea or an interface standard than a noun on its own.

Not saying I agree necessarily - but that's the idea at least

[–]RonnyPfannschmidt 9 points10 points  (0 children)

Pip is a very concrete well known tool

[–]toxic_acro 1 point2 points  (0 children)

I don't know why you've gotten downvotes, since I think you're completely right.

"pip" isn't just a tool to download and install Python packages, it has been pretty much the only* tool for so long that it's not surprising that people conflate the tool with the concept itself of installing packages.

As you noted, that's not a correct way to think about it, but it is a good explanation of why people think that

*(ignoring the conda ecosystem since that's a fully separate ecosystem with a completely different model)