On Sun, 2008-12-14 at 21:41 -0800, Mike Orr wrote: > > On Sun, Dec 14, 2008 at 8:38 PM, Iain Duncan <iaindun...@telus.net> wrote: > > > > Hi folks, I totally do not want to start a flame war here, but was > > wondering if people could give me their reasons for preferring buildout > > or virtualenv for automated builds of pylons apps or other wsgi apps. > > Virtualenv is more popular because it follows traditional Python usage > for the most part. You install packages interactively and can change > your mind at any time. Buildout's configuration recipes are hard for > many people to memorize, and it's more suited to situations where you > know ahead of time exactly which libraries you'll need You can > change the configuration and rebuild the environment from scratch, but > it's not as easy as installing an experimental package, trying it out, > and then uninstalling it if you don't like it.So with virtualenv you > can use the same tools for development as you use for deployment, > whereas buildout is more of a deployment-only thing.
Thanks Mike, that's exactly the kind of feedback I'm looking for. What do you use for automating virtualenv based deployments/builds? > > On the other hand, buildout has some features virtualenv doesn't, like > an egg cache. You can have it build up a shared cache of eggs you've > installed, which it can pull from for later installs. Could you tell me why this is sometimes advantageous? Thanks Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
