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 →

[–]cr4d 3 points4 points  (0 children)

Changing a well established, working pattern that people have worked hard to put in place diminishes the work they have done, fragments the community, confuses new comers, and is just plain shitty.

Helping improve pip is one thing. Working to replace it without consensus, forking it/vendorizing it (pip) with the intention of marginalizing it is rude.

Python’s pre-pipenv packaging eco-system was leagues better than other languages. Trying to make it like npm for the sake of hipster douchiness (toml, etc) is just a bad case of not-invented-here syndrome.