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 On Friday, October 12, 2012 6:00:22 PM UTC+2, Tom Evans wrote: > > On Fri, Oct 12, 2012 at 4:45 PM, Tomáš Ehrlich > <tomas....@gmail.com<javascript:>> > 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 > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/87wbyhQSQPUJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
