On 6/3/06, Jeff Forcier <[EMAIL PROTECTED]> wrote: > > Jay Parlar wrote: > > > 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. > > Well, assuming you implemented it with a simple 'RESTful' > ping-a-URL-and-get-something-back view method, you can easily debug it > by finding out what exact URL the JavaScript accessed (pretty sure > runserver tells you this on the console?), and manually going there in > your browser. Then you will see the normal Django error message. Took > me a short while to figure this out myself, probably because it was so > simple it didn't even occur to me at first =)
D'oh, I didn't think of that. However, in my particular case, it wouldn't have worked, because I needed Session information that was generated from previous views. Although I guess for debugging purposes, I could have probably faked the Session part. 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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
