Re: [Fab-user] fabric.api missing from module index.

[Jorge Vargas]

Hi,

I must have missed this response.

>From the usage point of view importing * from api seems great. However
since you do that while looking at the docs you will need to figure
out in which package the actual function is. Which basically means
clicking every link in
http://fabric.readthedocs.org/en/1.3.3/index.html#core-api and
scouting for hte function you actually need, specially if you are
new/don't remember well the exact name of each function.

On Sun, Nov 27, 2011 at 4:49 PM, Jeff Forcier <address@hidden> wrote:
>> I was wondering if this was left out on purpose.
>
> Pretty much -- it would be duplicative. Anything listed under "Core
> API docs" on the main page, is in fabric.api. So "from fabric.api
> import *" gets you all the decorators, context managers, operations
> etc (in one flat namespace.)
>
> If you can elaborate on your use case re: looking things up and why
> it's not working for you, we're always open to docs improvements.
>
> Thanks,
> Jeff
>
> --
> Jeff Forcier
> Unix sysadmin; Python/Ruby engineer
> http://bitprophet.org