4 ms·
> 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
by oneweekwonder 9y ago
> 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/ https://www.python.org/dev/peps/pep-0405/
[1] https://virtualenv.pypa.io/en/stable/changes/#id54 https://virtualenv.pypa.io/en/stable/changes/#id54
- masklinn 9y agovirtualenv solved conflicting dependencies but pip is what made installing & managing them convenient. I see many people who use pip without virtualenvs.
- oneweekwonder 9y agoTrue, 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!
- masklinn 9y agoYeah 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.