> I'm not sure how I feel about this. In the case of a library that is > managed by someone else and isn't going to be Sphinx-documented, that's > fine (e.g., simplejson, as I don't know if there's any plans to change > over its docs). But if webob documentation gets mirrored all over the > place, that does bother me a bit. I dislike the ambiguity of the > situation, where you could google for webob docs and get identical docs > at a variety of locations, and easily come upon documentation for old > versions without realizing that's what you had gotten.
One of the points of Pylons and similar projects is to create integrated package of many smaller components. Building aggregated self-contained docs is important part of such an effort. So, IMO, unless there are licence issues, it is good idea to build such an aggregated documentation set. Of course one can add a sentence about master page here or there. PS And it would be truly beautiful if there existed single pretty PDF file which would allow one to print 'everything he needs...'. -- ---------------------------------------------------------------------- | Marcin Kasperski | Communication takes place between people, | http://mekk.waw.pl | documents are secondary. (Booch) | | ---------------------------------------------------------------------- _______________________________________________ Paste-users mailing list [email protected] http://webwareforpython.org/cgi-bin/mailman/listinfo/paste-users
