On Tue, Jan 12, 2010 at 12:02 PM, eegg <[email protected]> wrote: > > Which brings me to my question: is there no interest in using tools > like sphinx in this regard, and if not, why? It seems architecturally > odd to me that both reST and sphinx provide many things which will > only be of use to code documentation.
As I understand it, Sphinx was created to fill a very specific need: documenting standard Python. As it happens, many of the features that are needed for that purpose are also useful for producing other kinds of texts. But there are also many features that are useful only for documenting code, or Python code in particular. Georg has wisely followed the strategy of only implementing features that somebody actually needs (and not necessarily all of those), rather than trying to make the tool generic to fill imagined needs. But following this strategy has resulted in a tool that is in fact generically useful. > So a second question: would it make more sense to anyone else out > there if the sphinx "python documentation generator" was a rather > thinner set of utilities built on top of a generalized formatting > suite? Sure, makes sense to me. And? What are you proposing? --Janet http://www.janetswisher.com
-- 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.
