Comments on: Python code management & deployment – a glance at zc.buildout and few others http://blog.mfabrik.com/2008/09/02/python-code-management-deployment-a-glance-at-zcbuildout-and-few-others/ Freedom delivered. Mon, 19 Sep 2011 19:02:42 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Tuukka Mustonen http://blog.mfabrik.com/2008/09/02/python-code-management-deployment-a-glance-at-zcbuildout-and-few-others/comment-page-1/#comment-432 Tuukka Mustonen Tue, 02 Sep 2008 20:59:22 +0000 http://blog.redinnovation.com/?p=104#comment-432 @ Tiberiue: I didn't mean buildout was difficult, but that it will take some time to learn. In that time you could have written a quick shell script and get well along with your project. I mean, if you want to just run some shell command, say 'netstat -r' and get the output, you need a recipe for that. Now how to create a recipe when you don't know how? Read through the docs and learn it, then debug some of the issues and try to resolve the rest of the things by looking at buildout source code. If we could do this with plain python it might take a lot less time. As for the package upgrading, yes, version/revision information does that but I'm just too lazy to write them up :) It's easier just to do the update for selected packages when I want it (maybe buildout could allow executing a single part from command line). @ Kevin: remote deployment sounds nice although it cannot replace the manual ssh'ing. Given a good set of tools, however, it might ease out lots of things. I definitely have to check that out then.. @ Tiberiue: I didn’t mean buildout was difficult, but that it will take some time to learn. In that time you could have written a quick shell script and get well along with your project. I mean, if you want to just run some shell command, say ‘netstat -r’ and get the output, you need a recipe for that. Now how to create a recipe when you don’t know how? Read through the docs and learn it, then debug some of the issues and try to resolve the rest of the things by looking at buildout source code. If we could do this with plain python it might take a lot less time.

As for the package upgrading, yes, version/revision information does that but I’m just too lazy to write them up :) It’s easier just to do the update for selected packages when I want it (maybe buildout could allow executing a single part from command line).

@ Kevin: remote deployment sounds nice although it cannot replace the manual ssh’ing. Given a good set of tools, however, it might ease out lots of things. I definitely have to check that out then..

]]> By: Kevin Dangoor http://blog.mfabrik.com/2008/09/02/python-code-management-deployment-a-glance-at-zcbuildout-and-few-others/comment-page-1/#comment-431 Kevin Dangoor Tue, 02 Sep 2008 13:06:52 +0000 http://blog.redinnovation.com/?p=104#comment-431 Hi Tuukka, Thanks for putting together a succinct overview of zc.buildout (which I think will be useful for a lot of folks who have never tried it) and for mentioning Paver. I've found Paver to be a great tool for scripting my projects. Just a thin layer over standard Python (rather than trying to build a DSL of sorts in an INI file). Currently in bzr on launchpad, Paver has grown support for Virtualenv+PoachEggs. In a couple of weeks, I'm planning to add some remote deployment support. That will really flesh out the deployment part of the picture for Paver. Kevin Hi Tuukka,

Thanks for putting together a succinct overview of zc.buildout (which I think will be useful for a lot of folks who have never tried it) and for mentioning Paver.

I’ve found Paver to be a great tool for scripting my projects. Just a thin layer over standard Python (rather than trying to build a DSL of sorts in an INI file).

Currently in bzr on launchpad, Paver has grown support for Virtualenv+PoachEggs. In a couple of weeks, I’m planning to add some remote deployment support. That will really flesh out the deployment part of the picture for Paver.

Kevin

]]> By: Tiberiu Ichim http://blog.mfabrik.com/2008/09/02/python-code-management-deployment-a-glance-at-zcbuildout-and-few-others/comment-page-1/#comment-430 Tiberiu Ichim Tue, 02 Sep 2008 12:58:49 +0000 http://blog.redinnovation.com/?p=104#comment-430 I've recently settled on this workflow when using buildout: create a new virtualenv project, install inside it zc.buildout, then run my buildout. If you're concerned with the fact that you get breakages from updating packages, you can either: specify a versions section in buildout.cfg, or run buildout with the -N switch, or specify versions for required packages inside your setup.py (if you're developing a new package). As the author of a zc.buildout recipe I can attest that writing one is not a very complex task and there are sufficient minimal examples to get you started. I’ve recently settled on this workflow when using buildout: create a new virtualenv project, install inside it zc.buildout, then run my buildout. If you’re concerned with the fact that you get breakages from updating packages, you can either: specify a versions section in buildout.cfg, or run buildout with the -N switch, or specify versions for required packages inside your setup.py (if you’re developing a new package). As the author of a zc.buildout recipe I can attest that writing one is not a very complex task and there are sufficient minimal examples to get you started.

]]> By: Antti Haapala http://blog.mfabrik.com/2008/09/02/python-code-management-deployment-a-glance-at-zcbuildout-and-few-others/comment-page-1/#comment-429 Antti Haapala Tue, 02 Sep 2008 10:50:36 +0000 http://blog.redinnovation.com/?p=104#comment-429 Shell scripts are sometimes difficult too. Let's not forget GNU make either; a single Makefile could more often than not be the easiest way to install dependencies... Shell scripts are sometimes difficult too. Let’s not forget GNU make either; a single Makefile could more often than not be the easiest way to install dependencies…

]]>