Hi Nat,<div><br></div><div>Thanks. I'm not desperate to see updated docs, just to get an idea of how to proceed. But it sounds as though regeneration is about due anyway.</div><div><br></div><div>Cheers<br clear="all">
<br>-- David<br>
<br><br><div class="gmail_quote">On 8 October 2012 14:47, Nathaniel Echols <span dir="ltr"><<a href="mailto:nechols@lbl.gov" target="_blank">nechols@lbl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Mon, Oct 8, 2012 at 3:48 AM, David Waterman <<a href="mailto:dgwaterman@gmail.com">dgwaterman@gmail.com</a>> wrote:<br>
> I've got a few questions about the automatically generated Python<br>
> documentation.<br>
</div>> ...<br>
<div class="im">> 3. Similarly, what determines which packages are documented or not? For<br>
> example, from <a href="http://cctbx.sourceforge.net/current/python/rstbx.html" target="_blank">http://cctbx.sourceforge.net/current/python/rstbx.html</a>, cftbx<br>
> is documented but bpcx is not. Is there at some point a manual decision<br>
> about what should be documented?<br>
<br>
</div>I think the partial answer is that the while the documentation is<br>
automatically generated, it is only updated on demand - i.e. someone<br>
needs to run a script to rebuild the online docs. �Not surprisingly,<br>
this hasn't been done since at least May. �I'll see if I can figure<br>
out how to do this today (which may help answer the other questions).<br>
<br>
-Nat<br>
_______________________________________________<br>
cctbxbb mailing list<br>
<a href="mailto:cctbxbb@phenix-online.org">cctbxbb@phenix-online.org</a><br>
<a href="http://phenix-online.org/mailman/listinfo/cctbxbb" target="_blank">http://phenix-online.org/mailman/listinfo/cctbxbb</a><br>
</blockquote></div><br></div>