On Sep 19, 2013, at 10:37 AM, Stuart Prescott wrote: >PPS Virtualenvs are another commonly cited use case for pip, but virtualenvs >are mostly a short way of saying "we don't care about API stability" (your >own story of the incompatibilities of django versions is an illustration of >this); they're an interesting technical solution to a poor development model >that focuses on developers getting high on finding the perfect solution at >the expense of the users of the code. Every user of that module has to >either: keep altering their own code to match new APIs, or try to insulate >their code from API changes by using virtualenvs, or NIH it instead. So >sure, virtualenv+pip is a valid use case for pip, but it should hardly be >considered the pinnacle of python's achievements. While I can't argue about the sentiment here, I'll just observe that this isn't really a problem solely for Python. It's an indictment of the state of software development today. Don't forget, we've only been doing this long enough to have the equivalent of heavy rocks and maybe the occasional pointy stick. It never ceases to amaze me that we can take down as many woolly mammoths as we do. -Barry
Attachment:
signature.asc
Description: PGP signature