Self._Dispatch(dispatcher, self.rfile, outfile, env_dict)įile "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/tools/dev_appserver.py", line 3149, in _Dispatchįile "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/tools/dev_appserver.py", line 525, in Dispatchįile "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/tools/dev_appserver.py", line 2402, in Dispatchįile "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/tools/dev_appserver.py", line 2312, in ExecuteCGI
#Google app engine sdk location mac full
Here is a full stack trace (this one uses the Kay framework, but the problem is the same with webapp): Traceback (most recent call last):įile "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/tools/dev_appserver.py", line 3206, in _HandleRequest
(Also, I can use the GoogleAppEngineLauncher to start my app.) If I deactivate the virtualenv and run that command with the system python2.5, it works. If I run python /usr/local/bin/dev_appserver.py with the virtualenv python, the problem persists.
I upgraded to virtualenv 1.5.1 today to try to fix the problem.
#Google app engine sdk location mac mac os
I am using the system Python that came with Mac OS X. Update: In response to Alan Franzoni's questions: But like I said, I had this working until last week.something changed or I inadvertently broke my virtualenv and I can't figure out how I got it working in the first place. It seems that the SDK's sandboxing is preventing these libraries from getting loaded. '/System/Library/Frameworks/amework/Versions/2.5/lib/python2.5/base64.py' If I start up python, I can load these modules. If I visit the admin console I get "ImportError: No module named cgi". The server starts but the first request errors out with the aforementioned "ImportError: No module named base64". Then I source my "foobar" virtualenv and try to start my app with dev_appserver.py. usr/local/google_appengine/lib/webob_1_1_1
usr/local/google_appengine/lib/fancy_urllib Then I add the a gae.pth file to ~/.virtualenv/foobar/lib/python2.5/site-packages/ containing the Google App Engine libraries: /usr/local/google_appengine Virtualenv -python=python2.5 -no-site-packages ~/.virtualenv/foobar When I setup a virtualenv for a Google App Engine app and start the app with dev_appserver.py, I get errors importing the standard library (like "ImportError: No module named base64"). I am pulling my hair out trying to figure this out because I had it working until last week and somehow it broke.
0 kommentar(er)
