On Jun 30, 10:46 am, Stéfan van der Walt <[email protected]> wrote: > 2009/6/30 Chris Withers <[email protected]>: > > >>http://pypi.python.org/pypi/SetupDocs/1.0.2 > > > This doesn't look like it uses Sphinx... > > It uses Sphinx (at least, I see Sphinx mentioned many times in the sources).
We wanted SetupDocs to be integrated into a setup.py such that it was runnable by everyone who has the project source tree, even though not everyone wants to rebuild the docs from source every time they do a local build, install, or generate a distribution. So what we did is make the SetupDocs source look for an install of Sphinx at runtime rather than have an absolute dependency on Sphinx. The algorithm is basically this: If Sphinx is found at runtime, generate the docs from source. Otherwise, unzip pre-built docs from a zip cache checked into the source tree. The idea of the latter is that everyone has some docs to use. It is up to the project participants to decide how often the pre-built cache gets checked in, and thus how current it is. Hope that helps! -- Dave --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
