I've never used Pyramid under windows, so I could be off here... But when running under Mac/Linux, one can trip 500x error that just says "Invalid Request" (or similar) under a few scenarios:
• exceptions in the wsgi middleware stack • exceptions in most areas of the debugtoolbar code • exceptions in very few areas of pyramid code (I think mostly in certain Events and Tweens) For the debugtoolbar to work (and show you the traceback) it needs to catch the exception. It can't catch the middleware errors, and raising exceptions in certain parts of pyramid code will not have a proper environment for the tracebacks to work. So these errors appear in the process log, but are inaccessible to the toolbar/interactive traceback mechanism. It sounds to me like this is what you're experiencing. Are you using any Event Subscribers ? ( I think I've triggered stuff like this with NewResponse can cause this ) I recall tweens having issues too. I think I also caused this with an exception in an __init__() function when using Class-based views. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
