doesn't embedding it in the sourcecode mean that you have to have your docs approved and committed to the trunk?
that adds another layer of redtape just to add a simple example of usage. it probably seems more "right", but there is no reason not to work it all out in the wiki and then once it is nice and approved then add it to the docstring later, not the other way around. Otherwise we get the autogenerated mess of "this is really hard to explain, we'll do it later." documentation is hard and it takes testing and thorough reading from multiple perspectives. the wiki is perfect for this. -1 for epydoc. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
