On Fri, Aug 10, 2007 at 08:59:04PM +0200, Raphael Hertzog wrote: > 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.
Hmmm. Yes, it's central, but a lot of the rest of it works with pydoc - I can see why this particular use case doesn't, but I'll take a looksee tomorrow incase there is an easy solution (I don't think there is, I think Raphael is spot on...) > > or else there needs to be a way to fix it from the pydoc side... > > Even more ugly. :-) Patching pydoc for a specific library isn't really a choice. Very messy and would end up with pydoc having far too many overrides. Thanks, -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
