On Fri, Mar 26, 2010 at 3:09 PM, Martin Raspaud <martin.rasp...@smhi.se> wrote: [..] > > Packaging an entire buildout environment is not really an option I think, > since > we have several projects using the same eggs, and we think it would be cleaner > to share them (I'm thinking especially of big eggs, like scipy and numpy). >
It really depends on your needs and constraints. I had to ship full releases to customers. In your case, you could share the same downloads and eggs folders on your productions servers maybe, or run your own PyPI private server to serve the archives to your buildouts when they claim it. [..] > > Buildout is interesting to me because I can develop, test and use packages in > a > clean environment. I don't need to take care of any PYTHONPATH, all > dependencies > are installed automatically, and so on. So it is a great tool for development, > and I got this from your book (which is really great by the way). Great to hear the book helps :) As a matter of fact, I wrote it right after I had set up a process for a generic release story with buildouts at a Plone company, to help developers ship their applications to the customers. > As such I want to have a recipe for automatically creating packages to deploy > on > our servers. > I see that it is indeed not buildout's philosophy build isolated eggs, but it > is > not the only thing I use it for :), it is a mere packaging tool for our > production system I am building. It makes sense. I use buildout for most web applications production environments, and I think many people do. It's just harder to sell if you have a sysadmin in front of you, that is used to other tools ;) Tarek _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
