Although it might be nice to have api docs online, you have to say that django has excellent high level docs (django docs site) and low lvl docs (code is well py-documented -in the source). Epydocs, and other doc alternatives - automatic or semi automatic doc generators like pydoctor, sphinx (a quick google search revealed quite a few free and nonfree python doc generators) are what i consider standard (python) programming tools, and it actually makes sense for the developer to do this "client" side (3rd party libaries, etc... all in one interface, and for the code version you are using, for example). The difficult, hard to write human documentation in django is excellent, btw :p
all that said, maybe we can take a look at trac plugins... http://trac-hacks.org/wiki/PyDocPlugin http://trac.edgewall.org/wiki/TracDev/ApiDocs i have no experience with them, maybe someone here has used them before? cheers, ashley On Jan 11, 9:59 am, Masklinn <maskl...@masklinn.net> wrote: > On 2011-01-11, at 09:36 , mrmclovin wrote:> If you bought a game, would you > rather like to get info on how to > > compile the game in order to play it.. or just install it and play it? > > This analogy makes no sense whatsoever, I fear. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
