Re: Unhandled exception during validation

[Tomáš Ehrlich]

Hello Oyvind,

that's weird, Django (or Python  in general) usually provide very long and descriptive trackback.

Could you please provide more information? What version of Python do you have? Does it fail when you run ./manage.py runserver? You've mentioned, the error is in local app, does that app load any thirdparty modules?

I've never came across unhandled exception which doesn't show trackback, so my guess is some c/c++ python extension (PIL, psycopg2, …). But that's just guess…

Cheers,

 Tom

Dne pátek, 12. října 2012 12:47:51 UTC+2 Oyvind Idland napsal(a):

Hello,

I am currently trying to upgrade a site from 1.2.x to 1.4.1. When I try to start the app, I get this:

Validating models...
Unhandled exception in thread started by <__main__.NewThreadStartup instance at 0x03D13738>


Since the output is very economical about info, I spent some time to track down the origins.
I found this in loading.py,  AppCache._populate():

            for app_name in settings.INSTALLED_APPS:
                if app_name in self.handled:
                    continue
                self.load_app(app_name, True)    <---- CRASH

The app it tries to load, is a local one (made by a co-developer some time ago).

Shouldn't there be better error handling in cases like this, at least showing what happened, and where ?
There is no exception handling what so ever..

-- Oyvind

[Tom Evans]

On Fri, Oct 12, 2012 at 4:45 PM, Tomáš Ehrlich <tomas....@gmail.com> wrote:
> Hello Oyvind,
> that's weird, Django (or Python in general) usually provide very long and
> descriptive trackback.
>
> Could you please provide more information? What version of Python do you
> have? Does it fail when you run ./manage.py runserver? You've mentioned, the
> error is in local app, does that app load any thirdparty modules?
>
> I've never came across unhandled exception which doesn't show trackback, so
> my guess is some c/c++ python extension (PIL, psycopg2, …). But that's just
> guess…
>
> Cheers,
> Tom

I think you've misunderstood the OP, the error occurs in Django's
AppCache, which is populated when you start django in any manner (even
going to the shell). The error occurs when AppCache tries to load one
of his custom apps, and the issue is that the error message does not
indicate the error that occurred, provide a proper traceback or even
indicate which app it failed to load.

(Sorry OP, haven't a clue)

Cheers

Tom

[Tomas Ehrlich]

Well, in this case, I don't see problem in erroritself (that happens).
I see problem in missing trackback (that's not usual). My assuption was
that "something" suppress it (don't know if it's possible, but I
assume it is).

Cheers,
Tom

Dne Fri, 12 Oct 2012 17:00:01 +0100
Tom Evans <teva...@googlemail.com> napsal(a):

S pozdravem
Tomáš Ehrlich

Email: tomas....@gmail.com
Tel: +420 608 219 889
Jabber: elv...@jabber.cz

"Půjdu kamkoliv, pokud je to kupředu." - J. London

[Oyvind Idland]

Sorry for the late reply !

Yes, you are correct. My point is, that something crashed somewhere, and there is no
stack trace or anything that indicates what the problem is.


-- Oyvind