On 23 nov, 23:33, Markus Barth <naturalparkdelseg...@gmail.com> wrote: > On 23 nov, 23:19, Javier Guerra Giraldez <jav...@guerrag.com> wrote: > > > On Tue, Nov 23, 2010 at 3:48 PM, Markus Barth > > > <naturalparkdelseg...@gmail.com> wrote: > > > I am using quite a lot of asynchronous calls for updating a page. The > > > problem is that this way you never see a traceback. In turbogears the > > > development server prints all tracebacks to the terminal. Is there any > > > way to get a similar behaviour with django? > > > firebug can show the content of any request/response, including AJAX > > ones. it also renders any HTML content, like those generated by the > > Django error pages > > > -- > > Javier > > This is only helpful if the request is answerered by the server, but > as soon as you have an exception, all you see on the console is a 500 > Error and Firebug tells you "status: aborted" > > For example I have just spend an hour chasing a bug just to find out > that syncdb didn't sync a table. With a traceback I would have seen > the problem within seconds > > Anyway, thanks for the hint
Sorry, I have to correct myself, in fact, I got the information through firebug. Thanks a lot, that saved my day. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
