Bug#436983: python-django: pydoc django.db blows up

2007-12-02 Thread James Bennett
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

Bug#436983: python-django: pydoc django.db blows up

2007-08-12 Thread Mark Eichin
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

Bug#436983: python-django: pydoc django.db blows up

2007-08-10 Thread James Bennett
Brett Parker wrote: 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...) There isn't really an easy soluti

Bug#436983: python-django: pydoc django.db blows up

2007-08-10 Thread Brett Parker
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 p

Bug#436983: python-django: pydoc django.db blows up

2007-08-10 Thread Raphael Hertzog
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.d

Bug#436983: python-django: pydoc django.db blows up

2007-08-10 Thread Mark Eichin
> by django-admin. I'm sorry that this behaviour is unfriendly towards pydoc > but I doubt there's any way to avoid this (without defining the variable > DJANGO_SETTINGS_MODULE to point to a valid Django settings module). As long as it stays open as a bug, that's fine; I suspect there *is* a way

Bug#436983: python-django: pydoc django.db blows up

2007-08-10 Thread Raphael Hertzog
severity 436983 minor tag 436983 + wontfix thanks On Thu, 09 Aug 2007, Mark Eichin wrote: > Package: python-django > Version: 0.96-1 > Severity: normal > > $ pydoc django.db > problem in django.db - EnvironmentError: Environment variable > DJANGO_SETTINGS_MODULE is undefined. All packages which

Bug#436983: python-django: pydoc django.db blows up

2007-08-09 Thread Mark Eichin
Package: python-django Version: 0.96-1 Severity: normal $ pydoc django.db problem in django.db - EnvironmentError: Environment variable DJANGO_SETTINGS_MODULE is undefined. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') A