News for hackers. Stuff that matters.
Re:Learning Go as a Node.js Developer by oneweekwonder on Friday February 09, 2018 @06:08AM (#16339360)
> much as it used to be in Python a few years back.

few years back being pre-2011, with pep 405[0] and virtualenv[1] solving most of the nostalgic py dep hell problems.

venv's been a option since 2007, only getting pep'ed later?

[0] https://www.python.org/dev/peps/pep-0405/

[1] https://virtualenv.pypa.io/en/stable/changes/#id54

Re:Learning Go as a Node.js Developer by masklinn on Friday February 09, 2018 @06:19AM (#16339393)
virtualenv solved conflicting dependencies but pip is what made installing & managing them convenient. I see many people who use pip without virtualenvs.
Re:Learning Go as a Node.js Developer by oneweekwonder on Friday February 09, 2018 @06:29AM (#16339424)
True, in my limited experience venv and pip goes hand in hand. But I can see use cases where you use them apart, more so with pip then venv.

Initial pip release was also 2011. Now I wonder what I used pre-pip?!

edit: easy_install, doh!

Re:Learning Go as a Node.js Developer by masklinn on Friday February 09, 2018 @06:58AM (#16339539)
Yeah easy_install, which theoretically worked (kinda), but alongside pip there was also the overall pypa effort (both marketing and technical) to make the whole thing work e.g. update or even fork the more abstruse projects such that they could actually be installed via pip. IIRC that was the primary reason for Pillow forking PIL.