On Fri, 2008-04-11 at 22:00 -0700, Mike Orr wrote: > On Fri, Apr 11, 2008 at 8:55 PM, Cliff Wells <[EMAIL PROTECTED]> wrote: > > The method I've been using is documented here: > > > > > > http://peak.telecommunity.com/DevCenter/EasyInstall#administrator-installation > > > > I'd like to add, that except for this one problem I've encountered, it's > > worked quite well for a few years now. I see virtualenv as solving a > > problem that was already solved by setuptools itself quite some time > > ago. > > This is going to be another of those "dumb users" issues we clashed > about before.
Not especially. I'm going to dodge it since it's clear you care about it far more than I do =) > Virtualenv, although it's not part of the stdlib, is straightforward > and self-contained. You don't have to modify the system Python > library to use it, so I don't see why you consider it incompatible > with your old environment. It is incompatible for one simple reason: these are existing applications. It's simply not feasible to reinstall a customer's application with no tangible benefit to them. Most of them don't care it's written in Python, let alone that it's not using virtualenv. They won't appreciate the "upgrade" and they certainly won't pay for it. So more or less, it's an exercise in busy work. Regards, Cliff --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
