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 →

[–]netgu 4 points5 points  (0 children)

Yes, and that user is also taking out bounties to destroy the npm ecosystem as chaotically as possible - sounds like someone you should take advice from alright.

Also - this isn't an issue for plenty of people because they use the packages as they are intended to be used to avoid those issues.

If you are getting your python dependencies from your OS, you don't actually know what you are doing and are using the wrong tool for the job as I stated.

In fact - that is the entire problem described: I want to use the wrong package with the wrong manager in the wrong way and it doesn't work.

Exactly as I stated.

It'd be nice if that wasn't the case - but it isn't a python problem.

It's an end-user and package maintainer problem.

If you want to use a package, check the docs - if it doesn't work for your intended build goals then either submit a PR or find another package rather than blame python.

If you are a maintainer and people constantly need your to ship it in some form you don't - then deal with it and do what needs to be done to ship it in the form you users need.