> It would be nice if you could do "python setup.py epydoc" in TG, reading > config settings from setup.cfg. If anyone is inclined towards such > things, the glue code is pretty small. But you have to use distutils > command line framework, which is a tad crufty (but not that bad, > really). Anyway, if anyone is curious about such things, I can point > you to example code.
For now I think we're still exploring all our options. Epydoc seems to just work right now, which is a huge benefit, but some of the other options will give more control over the output format, which I think is a good thing. It would also be great to see something that TG+Pylons+Paste could standardize on. I really don't know what we should do ultimately, but I think we should continue to explore our options for a couple weeks at least. --Mark --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
