su, 2009-10-25 kello 10:41 -0400, Darren Dale kirjoitti:
> On Sun, Oct 25, 2009 at 10:17 AM, Darren Dale <[email protected]> wrote:
> > On Fri, Jul 31, 2009 at 10:19 PM, Richard West <[email protected]> wrote:
> >> The documentation at
> >> http://sphinx.pocoo.org/latest/ext/autosummary.html#confval-autosummary_generate
> >> suggests autosummary_generate can be a boolean saying whether to scan
> >> all found documents (and/or it can be an iterable list of documents to
> >> scan) but when I set autosummary_generate = True I get the following
> >> exception. It seems the extension only expects an iterable list of
> >> documents to scan.
> >>
> >> Exception occurred:
> >>  File "/Library/Frameworks/Python.framework/Versions/2.5/lib/
> >> python2.5/site-packages/Sphinx-0.6.2-py2.5.egg/sphinx/ext/autosummary/
> >> __init__.py", line 311, in process_generate_options
> >>    for genfile in genfiles]
> >> TypeError: 'bool' object is not iterable
> >
> > I see this same thing with sphinx-0.6.3. Could someone offer any
> > advice on how autosummary_generate should be used? I added
> > "autosummary_generate = True" to my conf.py, is that not right?
> >
> 
> I think this is a bug.
> http://sphinx.pocoo.org/ext/autosummary.html#confval-autosummary_generate
> says:
[clip]

The version of autosummary in Sphinx's 0.6.x branch is a bit outdated.
The tip version contains significant feature additions (from last May,
or so), and for example, the possibility to use booleans.

The documentation on the Sphinx website is for the Sphinx 0.6.x branch,
and corresponds to the tip version of autosummary, whereas 0.6.3 still
has the old one.

-- 
Pauli Virtanen



--~--~---------~--~----~------------~-------~--~----~
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]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/sphinx-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to