On Tue, Jul 12, 2011 at 10:23 AM, Jonas Geiregat <jo...@geiregat.org> wrote: > Hello, > > I really love django's documentation. It covers a lot of ground and is really > well written. > I do have one problem with it. It might be best explained with an example. > > I want to see all methods and properties of the request parameter in the > view. Search the docs for "request" doesn't help me much. In fact searching > the docs for a particular method often doesn't point me to the correct page. > > What I sometimes need is a tree view of all django's modules, classes, > methods and properties. It also might help me better understand the structure > of how django was written. > > Is there something like that out there ?
Not really. You can run epydoc over the django source to generate such a view if you want. I believe that this is not offered by design; by offering internal API docs, people will then start to use previously 'undocumented' APIs, which then need to be supported. Basically, if you can find a reference to a function/class/attribute in the django docs at the moment, that function/class/attribute will be there in the next version, or will be discussed in the change log. This allows things like the internal SQL compiler to be changed significantly between 1.2 and 1.3 without any noticeable effects on users. The easiest way to investigate what attributes/methods a class has is to read the source. HttpRequest is here: https://code.djangoproject.com/browser/django/tags/releases/1.3/django/http/__init__.py Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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.
