News for hackers. Stuff that matters.
Re:PyCon 2015: Are we still changing the world? by carrja99 on Monday May 11, 2015 @11:42AM (#9525541)
The key difference between pypi and npm is that if you pull a package down and it depends on something==1.0.2 and you depend directly on the incompatible something==0.8.9 both version live together in peace because only request will use 1.0.2. With pypi (and most other dependency management systems) you'll have to make a choice on which one you want to use and in this example you'll have to choose an older version of the library depending on something==1.0.2.
Re:PyCon 2015: Are we still changing the world? by abstractbeliefs on Monday May 11, 2015 @12:13PM (#9525787)
This has been largely solved with virtualenvs where those collisions happen on the system level, but I concede it's harder when the mutually incompatible requirements are in the same project.
Re:PyCon 2015: Are we still changing the world? by tedmiston on Monday May 11, 2015 @12:39PM (#9525995)
If I'm understanding the question correctly, I agree virtualenv + virtualenvwrapper solves it mostly. For what I consider a decent treatment of some of the shortcomings in pip vs. npm, I found this post helpful:

"Things I wish Pip learned from Npm" https://medium.com/@alonisser/things-i-wish-pip-learned-from...