On Thu, Sep 17, 2009 at 8:48 AM, Mike Orr wrote:
>
> And how to you arrange for Sphinx to import the package it's
> documenting if it's in a sibling directory or parent directory of the
> docs directory? Righit now I think it's documenting the webhelpers in
> my virtualenv, but what I really wan
Hi,
On Thu, Sep 17, 2009 at 8:08 AM, Mike Orr wrote:
>
> So now I'm trying to generate the module docs to WebHelpers and am
> running into the same problem: there's a link to the top-level module
> but its page is blank. Currently I have:
>
> .. automodule:: webhelpers
>
> So I looked in the Be
And how to you arrange for Sphinx to import the package it's
documenting if it's in a sibling directory or parent directory of the
docs directory? Righit now I think it's documenting the webhelpers in
my virtualenv, but what I really want it to do is to document the
package in the source.
--
Mi
So now I'm trying to generate the module docs to WebHelpers and am
running into the same problem: there's a link to the top-level module
but its page is blank. Currently I have:
.. automodule:: webhelpers
So I looked in the Beaker package, and it has an
autoclass/autofunction for every single i
