[google-appengine] Re: Strange production only problem

2009-07-07 Thread Nick Johnson (Google)
Hi techboy, App Engine uses a custom Python environment, and as such, things like the search path may differ. For example, if you execute "sys.path" on shell.appspot.com, you get: ['/base/python_dist/lib/python25.zip', '/base/python_lib/versions/third_party/django-0.96', '/base/python_dist/lib/p

[google-appengine] Re: Strange production only problem

2009-07-06 Thread techboy
Thanks Nick for your reply. Is the python module search path different in production, than a standard client install? Because on my local machine, the current directory is first in the search path, and "import profile" from within the SDK loads profile.py from my project. Thanks again. On Jul 6,

[google-appengine] Re: Strange production only problem

2009-07-06 Thread Nick Johnson (Google)
Hi techboy, It's not a sandboxing issue - it's all down to the Python search path. System directories are listed before your own source directories, so it searches them first. You can change it by modifying sys.path if you wish. -Nick Johnson On Mon, Jul 6, 2009 at 5:12 AM, techboy wrote: > > T

[google-appengine] Re: Strange production only problem

2009-07-05 Thread techboy
The problem appears to be that the file in my project is named profile.py. There is also a profile.py in the python distribution itself. I'm assuming that it is a sandboxing restriction(?), that I can't import my own profile.py in production (even though it works fine in the dev appserver). In p