This is endemic with all asynchronous Javascript work, no matter what the back-end.
You have to make sure to trap both successes and failures in the Javascript code -- I don't know how mochikit does that, but with prototype you need to specify an onFailure hook to get errors. Regards, -scott On Sat, 2006-06-03 at 11:23 -0400, Jay Parlar wrote: > I was playing around with mochikit and Django yesterday, and was > getting really frustrated by one particular aspect: > > In any view code that was only responding to async requests, if I had > a typo or error in my Python code (anything that would raise an > exception), I wasn't seeing any exceptions *anywhere*. Usually of > course, Django sends the exception information back to the client, to > be displayed on screen. Doesn't work so well when some JS is expecting > the response. > > This was using the dev server and DEBUG=True. Maybe I missed something > in terms of how to get useful output, but it'd be nice if there were a > decorator or something that could tell Django that the client > expecting a response is *not* going to be able to display that > response, and the exception info should be displayed on the terminal. > > Just my two cents, > Jay P. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
