Re: [Fab-user] How about including an init command?

[Taras Mankovski]

Hey Jeff,

You're right. After I wrote, the email, I thought about it and
realized it's really only 1 or 2 lines.

But it would still save a few steps and it would be very easy to write.

With buildout when you run

buildout init

it creates 4 directories and empty buildout.cfg file.

I really appreciate the fact that you're so dedicated to keeping fab
on topic and from becoming bloated. I think that's great.

Let me know if you feel that this might be useful, if not then it's
ok, I'll just write something simple and throw it in my bin directory.

Thank you,
Taras

On Wed, Oct 14, 2009 at 7:52 PM, Jeff Forcier <address@hidden> wrote:
> Hey Taras,
>
> Can you give an example of "all the imports"? Offhand the only ones
> you might want to have in every fabfile would be:
>
>    from __future__ import with_statement # on 2.5 only
>    from fabric.api import * # "bad practices" but useful for us
>    from fabric.contrib.x import y # pretty situational really
>
> Given that the 3rd line isn't part of the real base package, that's
> only 2 lines (and only one line on Python 2.6!) :)
>
> If your concern is to avoid the "from anything import *", then the
> issue is that best practice vs code generation (a non-best practice
> typically) and honestly I'd say code generation loses that particular
> battle ;)
>
> Let me know your particular situation, though.
>
> -Jeff
>
> On Wed, Oct 14, 2009 at 6:53 PM, Taras Mankovski <address@hidden> wrote:
>> Hey Jeff,
>>
>> It would be great to be able to run init and it would generate a
>> fabfile.py with all of the imports.
>>
>> It would save some copy and pasting from other scripts or looking for
>> the import statements.
>>
>> What do you think?
>>
>> Taras
>>
>>
>> _______________________________________________
>> Fab-user mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/fab-user
>>
>