On Sat, Apr 12, 2008 at 6:44 PM, Cliff Wells <[EMAIL PROTECTED]> wrote: > > virtualenv is very much meant to keep working code working, and I think > > it does that. So there is a current answer to that problem. > > Yes, I'm turning around on virtualenv. Unfortunately there's not a lot > to be done for legacy installs but it will certainly be a consideration > for new installs.
By the way, what do you think of Buildout? We're debating whether to recommend virtualenv or buildout for people trying out Pylons. Most of our experience has been with virtualenv, but Buildout's cached eggs would be a nice feature for those who have several similar sandboxes. It seems like the main problem with Buildout is documentation, which can be fixed. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
