Then epydoc is very useful... useful to find problems with the docstrings!
On May 13, 3:52 pm, Jonathan Lundell <jlund...@pobox.com> wrote: > On May 13, 2010, at 1:47 PM, mdipierro wrote: > > > True but there is always epydoc > > >http://web2py.com/examples/static/epydoc/ > >http://web2py.com/examples/static/epydoc/web2py.gluon.validators-modu... > > I've always found the source easier to read than epydoc. And the summaries > leave a lot to be desired. Here's a current example: > > IS_EMPTY_OR > dummy class for testing IS_EMPTY_OR > IS_NULL_OR > dummy class for testing IS_EMPTY_OR > > Now that's helpful. > > My point with the book is that the information is already there, but > scattered and hard to find. > > > > > On May 13, 3:22 pm, Jonathan Lundell <jlund...@pobox.com> wrote: > >> On May 13, 2010, at 1:01 PM, weheh wrote: > > >>> @mdp: thanks for the clarification. I like having 1 way of doing > >>> things, which is why I dumped perl years ago. Perhaps IS_NULL_OR > >>> should be officially deprecated? > > >> Is there a place for that? It'd be nice to be able to look that up. Maybe > >> an appendix in the book. IS_NULL_OR isn't the only one. > > >> Speaking of appendices in the book, in the last editing round I recall > >> suggesting that there should be a section that collected the various bits > >> & pieces of API from the rest of the book. Function signatures, list of > >> validators, what not.
