Hmm... i was checking against the github master. Maybe that's why it
worked for me?
On Tue, Dec 8, 2009 at 5:35 PM, Marco Rogers <marco.rog...@gmail.com> wrote:
> I would've thought so too. But I got an error when trying to access it
> through fabric.api. Thought it might've made a difference that i was doing
> a * import but that shouldn't matter and it didn't when I tested. Are you
> saying this is a bug?
>
> from fabric.api import *
> output['debug'] = True
> NameError: name 'output' is not defined
> ####
> from fabric.api import output
> output['debug'] = True
> ImportError: cannot import name output
> ####
> from fabric.state import output
> output['debug'] = True
> {'status': True, 'running': True, 'stderr': True, 'warnings': True, 'debug':
> True, 'aborts': True, 'stdout': True}
>
> On Tue, Dec 8, 2009 at 11:26 AM, Christian Vest Hansen
> <karmazi...@gmail.com> wrote:
>>
>> Yes, it is defined in fabric.state but also exposed through fabric.api.
>>
>> The fabric.api module is, you know, the api :p
>>
>> On Tue, Dec 8, 2009 at 4:18 PM, Marco Rogers <marco.rog...@gmail.com>
>> wrote:
>> > Actually I found the output dict is in fabric.state. But that works
>> > like a
>> > charm. Thanks.
>> >
>> > On Mon, Dec 7, 2009 at 5:50 PM, Christian Vest Hansen
>> > <karmazi...@gmail.com>
>> > wrote:
>> >>
>> >> You can map the "debug" key on the fabric.api.output dict to True,
>> >> like in this example:
>> >>
>> >> from fabric.api import local, output
>> >> output['debug'] = True
>> >>
>> >> def go():
>> >> local("echo hi", capture=False)
>> >>
>> >> And you can also use the --show=debug command-line argument.
>> >>
>> >> I don't think you can control this from .fabricrc, but I could be
>> >> wrong.
>> >>
>> >> On Mon, Dec 7, 2009 at 10:04 PM, Marco Rogers <marco.rog...@gmail.com>
>> >> wrote:
>> >> > I'm recently getting familiar with context managers in python. I'd
>> >> > like
>> >> > to
>> >> > be able to set the debug output option globally for my fabfile script
>> >> > instead of doing "with show('debug'):" in every task. Ideally I
>> >> > could
>> >> > set
>> >> > it in the .fabricrc, but if I can update the global context at the
>> >> > top
>> >> > of
>> >> > the script that'd be just as well. Are either of these currently
>> >> > possible
>> >> > and if so, what's the syntax?
>> >> > Sorry if I missed this in the docs, but I went over them pretty
>> >> > thoroughly
>> >> > and it doesn't seem to address this particular task.
>> >> > Thanks, really liking fabric
>> >> > :Marco
>> >> >
>> >> > --
>> >> > Marco Rogers
>> >> > marco.rog...@gmail.com
>> >> >
>> >> > Life is ten percent what happens to you and ninety percent how you
>> >> > respond
>> >> > to it.
>> >> > - Lou Holtz
>> >> >
>> >> > _______________________________________________
>> >> > Fab-user mailing list
>> >> > Fab-user@nongnu.org
>> >> > http://lists.nongnu.org/mailman/listinfo/fab-user
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Venlig hilsen / Kind regards,
>> >> Christian Vest Hansen.
>> >
>> >
>> >
>> > --
>> > Marco Rogers
>> > marco.rog...@gmail.com
>> >
>> > Life is ten percent what happens to you and ninety percent how you
>> > respond
>> > to it.
>> > - Lou Holtz
>> >
>>
>>
>>
>> --
>> Venlig hilsen / Kind regards,
>> Christian Vest Hansen.
>
>
>
> --
> Marco Rogers
> marco.rog...@gmail.com
>
> Life is ten percent what happens to you and ninety percent how you respond
> to it.
> - Lou Holtz
>
--
Venlig hilsen / Kind regards,
Christian Vest Hansen.
_______________________________________________
Fab-user mailing list
Fab-user@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fab-user
