Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #40069 > unrolled thread
| Started by | John Gordon <gordon@panix.com> |
|---|---|
| First post | 2013-02-27 17:31 +0000 |
| Last post | 2013-02-27 17:31 +0000 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
Django error tracebacks John Gordon <gordon@panix.com> - 2013-02-27 17:31 +0000
| From | John Gordon <gordon@panix.com> |
|---|---|
| Date | 2013-02-27 17:31 +0000 |
| Subject | Django error tracebacks |
| Message-ID | <kglft4$39i$1@reader1.panix.com> |
I've been developing in Django for a while now and I often find that when
there is an exception in a view I'm working on, the error traceback screen
does not show the actual error; instead it claims the error occurred in
django itself (usually .../django/core/handlers/base.py).
Why is this?
(I'm using Django 1.3 instead of the current 1.4 version, but still, this
seems like a pretty basic thing to get wrong.)
--
John Gordon A is for Amy, who fell down the stairs
gordon@panix.com B is for Basil, assaulted by bears
-- Edward Gorey, "The Gashlycrumb Tinies"
Back to top | Article view | comp.lang.python
csiph-web