Re:Fabric Python with Cleaner API and Parallel Deployment
by tswicegood on Tuesday February 22, 2011 @12:51PM
(#2250727)
That's an interesting idea. I like the idea of turning things off too. In some cases, that's more useful than explicitly defining a @task. Care to open a ticket on code.fabfile.org with it? Maybe we can work that in as an option in 1.1 (when @task is set to hit).
[ Parent
| on HN ]
Re:Fabric Python with Cleaner API and Parallel Deployment
by jsdalton on Tuesday February 22, 2011 @01:07PM
(#2250799)
Sure, I'll try to file one later so it can at least be considered.
What I was trying to say in my earlier comment was that I would actually prefer the explicit @task decorator be part of the official Fabric API because it's more clear and, well, explicit. I prefer my @internal decorator as a hack in the meantime because I imagine it's less surprising to someone who might stumble upon my fabfile without any explanation from me.
Re:Fabric Python with Cleaner API and Parallel Deployment
by bitprophet_ on Tuesday February 22, 2011 @01:12PM
(#2250826)
Yea, definitely add a link to that in http://code.fabfile.org/issues/show/76 please! Might be nice to give people even more control. I think @task is "enough" but if we can have a richer API while not overburdening things, could be a plus.