2 ms·
Not every company has the luxury of going "Oh, that's cool, we'll just completely switch to virtualenv for everything and start rolling our own RPMs." /magicwan
by pdeuchler 14y ago
Not every company has the luxury of going "Oh, that's cool, we'll just completely switch to virtualenv for everything and start rolling our own RPMs." /magicwand
Sometimes the best solution to your problem is economically untenable, sometimes you currently don't have the engineering talent to allocate, etc etc.
- hynek 14y agoAnd what exactly has that to do with Python 3.3? You spoke about overwriting CentOS’ /usr/bin/python with Python 3 but don’t have enough “engineering talent” to do proper deployments? You speak about economical factors, but doing broken deployments and using ancient Python versions (I’m talking 2.4 vs. 2.7 here, not Python 3) costs you much more money on the long run than building a new RPM every few months. Nevertheless 2.7 (which was released two years ago) still gets bug fixes and no new features. So I really don’t get what this comment thread is about.