On closer inspection - django.db only *has* two functions and they
don't have any docstrings :-) though presumably the __import__ changes
that by pulling them in from django.db.backends.*.base.
It could be argued, then, that a sufficient fix to the original
problem would be to include a pointer to real
documentation... *preferably* another pydoc option, but really it's
enough to have something that lets me say "ok, I've gotten far enough
in the tutorial that I have a models.py that says
from django.db import models
What does that actually mean? What methods do I have?"
ie. something specific, not just "go to django.org".
> Patching pydoc for a specific library isn't really a choice. Very messy
> and would end up with pydoc having far too many overrides.
Oh, certainly - I meant having pydoc supply some hint (a global? a
special entry in sys.modules?) that could be tested by "special"
packages like this, assuming it doesn't already.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
