I do not understand why don't they check the Python version and report
a wrong version as an error?

On 10 Lug, 23:32, MikeEllis <michael.f.el...@gmail.com> wrote:
> Solved.  GAE doesn't like 2.6 on OS X.   Changing to 2.5 via the
> Preferences dialog in Launcher fixed it (but I had to quit and restart
> the Launcher app for it to take effect).  More on this issue 
> athttp://code.google.com/p/googleappengine/issues/detail?id=985
> if anyone cares.
>
> Cheers,
> Mike
>
> On Jul 10, 11:52 pm, MikeEllis <michael.f.el...@gmail.com> wrote:
>
> > I'm trying to get started with GAE.  Just downloaded GAE SDK 1.3.5 and
> > installed on OS X 10.6.4.
>
> > Seems to be working for a trivial hello world example that doesn't use
> > web2py but I can't get any of my web2py apps to run, even a brand new
> > one created with the admin interface.  Dies importing from gluon.tools
> > with the following error:
>
> > Traceback (most recent call last):
> >   File "/Users/mellis/web2py/gluon/restricted.py", line 178, in
> > restricted
> >     exec ccode in environment
> >   File "/Users/mellis/web2py/applications/hellogae/models/db.py", line
> > 29, in <module>
> >     from gluon.tools import *
> >   File "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/
> > GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/
> > google/appengine/tools/dev_appserver.py", line 1286, in Decorate
> >     return func(self, *args, **kwargs)
>
> > ------- < SNIP > -----
>
> >   File "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/
> > GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/
> > google/appengine/tools/dev_appserver.py", line 1789, in
> > LoadModuleRestricted
> >     description)
> >   File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/
> > python2.6/ctypes/__init__.py", line 10, in <module>
> >     from _ctypes import Union, Structure, Array
> > ImportError: No module named _ctypes
>
> > Not sure what's going on.
> > * All apps run fine on localhost under rocket.py
> > * I can open python on the command line and execute the failing import
> > statement without error.
>
> > What dumb thing have I overlooked?
>
> > Thanks,
> > Mike

Reply via email to