Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #40069
| Path | csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!us.feeder.erje.net!news.snarked.org!xmission!newsswitch.lcs.mit.edu!bloom-beacon.mit.edu!panix!gordon |
|---|---|
| From | John Gordon <gordon@panix.com> |
| Newsgroups | comp.lang.python |
| Subject | Django error tracebacks |
| Date | Wed, 27 Feb 2013 17:31:16 +0000 (UTC) |
| Organization | PANIX Public Access Internet and UNIX, NYC |
| Lines | 15 |
| Message-ID | <kglft4$39i$1@reader1.panix.com> (permalink) |
| NNTP-Posting-Host | panix2.panix.com |
| X-Trace | reader1.panix.com 1361986276 3378 166.84.1.2 (27 Feb 2013 17:31:16 GMT) |
| X-Complaints-To | abuse@panix.com |
| NNTP-Posting-Date | Wed, 27 Feb 2013 17:31:16 +0000 (UTC) |
| User-Agent | nn/6.7.3 |
| Xref | csiph.com comp.lang.python:40069 |
Show key headers only | View raw
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 comp.lang.python | Previous | Next | Find similar | Unroll thread
Django error tracebacks John Gordon <gordon@panix.com> - 2013-02-27 17:31 +0000
csiph-web