On Aug 10, 2007, at 12:22 PM, Mark Eichin wrote:
As long as it stays open as a bug, that's fine; I suspect there *is* a way to work around it on the django side (for example, can it tell that pydoc is importing it?) or else there needs to be a way to fix it from the pydoc side...
Just a heads-up: upstream in Django changeset 6832 [1] we've changed the behavior from raising EnvironmentError to raising ImportError, which pydoc will happily smother as part of walking a tree of modules. You'll still need to have DJANGO_SETTINGS_MODULE set (or manually configure settings) in order to *use* Django, but I believe this deals with the cases where we inadvertently made pydoc explode.
[1] http://code.djangoproject.com/changeset/6832 -- James Bennett [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
