On Fri, 10 Aug 2007, 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?)
There probably is (via the "inspect" package), but I wouldn't want to patch django.db to detect this corner use case. This module is a central one in Django and if I were the upstream author, I'd rather not put such hacks in it. > or else there needs to be a way to fix it from the pydoc side... Even more ugly. :-) Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/
