I'm not exactly sure what you mean by "package docs". If you mean if
Apydia is able to generate complete documentation from like a couple
of rst-files in eg. a doc-folder, just the way like pudge does, I'll
have to disappoint you.
Apydia generetes API reference documentation, nothing more (by
intention). That's, by the way, the reason for the slightly modified
die hard quote at the top of the website.
Greetings,
--
Daniel Haus
http://ematia.de
Am 11.12.2007 um 13:09 schrieb Rob Cowie:
> Should apydia be able to descend into the package and produce the
> appropriate documentation? I have defined __all__ in the top-level
> __init__.py so sub modules are explicitly listed.
So, the modules are listed in __all__. Hm, and they are imported in
this place, too? Would you let me have a look on your package/
__init__.py?
> The modules are not imported in __init__.py, merely listed in __all__
> so that on 'from package import *', they are imported.
>
> I will try importing them although this is not the behaviour I require
> from this package. I don't really want the sub modules to be imported
> into the app namespace when the package is imported.
Then you will (currently) have to specify all packages as arguments to
the "apydia"-command (or in the apydia-section your setup.cfg). Btw.
there's a __doc_all__ property which you can set instead of __all__
(or additionally).
I'll work on making Apydia handle this in a more intelligent way.
Thank you for showing this up.
> Hey Daniel,
>
> looks good here, exclude_modules work as expected, too.
>
> Happy New Year!
>
> Andi
Great! Happy New Year!