What steps will reproduce the problem?
1. change app.yaml to (as below) with guestbook.py example
2. run
3.
What is the expected output? What do you see instead?
Am expecting it to run as per 2.5
I get this stack trace instead :
ERROR 2012-02-04 00:16:16,220 traceback.py:13] Traceback (most recent call
last):
ERROR 2012-02-04 00:16:16,220 traceback.py:13] File
"D:\Python27\lib\wsgiref\handlers.py", line 85, in run
ERROR 2012-02-04 00:16:16,220 traceback.py:13] self.result =
application(self.environ, self.start_response)
ERROR 2012-02-04 00:16:16,220 traceback.py:13] File "D:\Program Files
(x86)\Google\google_appengine\lib\webapp2\webapp2.py", line 1519, in __call__
ERROR 2012-02-04 00:16:16,221 traceback.py:13] response =
self._internal_error(e)
ERROR 2012-02-04 00:16:16,221 traceback.py:13] File "D:\Program Files
(x86)\Google\google_appengine\lib\webapp2\webapp2.py", line 1511, in __call__
ERROR 2012-02-04 00:16:16,221 traceback.py:13] rv =
self.handle_exception(request, response, e)
ERROR 2012-02-04 00:16:16,221 traceback.py:13] File "D:\Program Files
(x86)\Google\google_appengine\lib\webapp2\webapp2.py", line 1505, in __call__
ERROR 2012-02-04 00:16:16,221 traceback.py:13] rv =
self.router.dispatch(request, response)
ERROR 2012-02-04 00:16:16,223 traceback.py:13] File "D:\Program Files
(x86)\Google\google_appengine\lib\webapp2\webapp2.py", line 1253, in
default_dispatcher
ERROR 2012-02-04 00:16:16,223 traceback.py:13] return
route.handler_adapter(request, response)
ERROR 2012-02-04 00:16:16,223 traceback.py:13] File "D:\Program Files
(x86)\Google\google_appengine\lib\webapp2\webapp2.py", line 1076, in __call__
ERROR 2012-02-04 00:16:16,223 traceback.py:13] handler =
self.handler(request, response)
ERROR 2012-02-04 00:16:16,226 traceback.py:13] TypeError: __init__() takes
exactly 1 argument (3 given)
What version of the product are you using? On what operating system?
1.05 on win server 2008 with python 2.7.2
Please provide any additional information below.
Attaching guestbook and app.yaml
Original issue reported on code.google.com by rich...@barcodebeasties.com on 4 Feb 2012 at 12:19
Original issue reported on code.google.com by
rich...@barcodebeasties.com
on 4 Feb 2012 at 12:19Attachments: