iftekharjoy / webapp-improved

Automatically exported from code.google.com/p/webapp-improved
Other
0 stars 0 forks source link

WSGIApplication()'s debug=True option does not work #34

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. initialize application instance by webapp2.WSGIApplication() with debug=True 
arg
2. run it on the dev_appserver.py
3. raise Exception() in a request handler.

What is the expected output? What do you see instead?
Expected output is stack trace on the browser.
I saw empty body status:500 error page.

What version of the product are you using? On what operating system?
Python 2.7.2 64bit
AppEngine SDK 1.6.0
Windows 7 SP1 64bit

Please provide any additional information below.
This document
http://webapp-improved.appspot.com/guide/app.html#debug-flag says:
>  When in debug mode, any exception that is now caught is raised and the stack 
trace is displayed to the client

Original issue reported on code.google.com by Hideki.Y...@gmail.com on 20 Nov 2011 at 1:07

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
This issue was closed by revision da20281cbba3.

Original comment by rodrigo.moraes on 31 Jan 2012 at 6:07

GoogleCodeExporter commented 8 years ago
It appears that this bug is back - unless revision da20281cbba3 hasn't been 
incorporated yet in the sdk (?)

Steps to reproduce: introduce any syntax error into any request handler, such 
as the "hello world" one in "Getting started" for python27

Expected output: stack trace
Actual output: http 500 internal sever error (on localhost server). Haven't 
tried it on app engine production server

Versions: SDK 1.0.7 06-26-2012 for Windows; python 2.7.3 Windows; Windows 7 up 
to date as of July 15 2012; Chrome latest.

Things I tried: Substituting the whole folder of the downloaded webapp2 at 
appengine/lib directory, for webapp2 2.5.1. Result: it gives server error even 
for correct handlers

Please help -- is there any workaround?  

Original comment by josei09 on 15 Jul 2012 at 3:09

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
This seems to have popped up again in Google App Engine 1.9.17 - see 
https://code.google.com/p/googleappengine/issues/detail?id=11557

Original comment by olof.bja...@gmail.com on 23 Dec 2014 at 12:39