I also am having the same problem. Did you ever get a solution to this? On Monday, May 17, 2010 at 10:48:42 AM UTC-4, Daniel Stutzbach wrote: > > I'm trying to use the coverage extension to check for functions I > missed while writing documentation, but I'm not having much luck. > _build/coverage/python.txt always contains: > > Undocumented Python objects > =========================== > > ... and nothing else, even if I deliberately delete some > documentation. > > If I use autodoc, it finds my modules and can generate rudimentary > documentation for them, so I know Sphinx can import my module. > > Presumably I'm doing something wrong, but I'm not sure where to start > looking. Any suggestions? A minimal example demonstrating the > coverage extension in practice would be helpful. I couldn't find one > using Google. > > -- > You received this message because you are subscribed to the Google Groups > "sphinx-dev" group. > To post to this group, send email to [email protected] > <javascript:>. > To unsubscribe from this group, send email to > [email protected] <javascript:>. > For more options, visit this group at > http://groups.google.com/group/sphinx-dev?hl=en. > >
-- You received this message because you are subscribed to the Google Groups "sphinx-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sphinx-users. For more options, visit https://groups.google.com/d/optout.
