6

I have created a folder with all my modules for my GAE application and with external libraries like Jinja2 to keep everything sorted in one place. I have folders structure like this:

lib\
   \utils\
         \__init__.py
   \firepython
   \jinja2
   \jsonpickle
   __init__.py
   sessions.py

When I try to load Jinja from utils__init__.py, I get error ImportError: No module named jinja2.environment. When I look at Jinja2 imports instructions, I see them look like from jinja2.loaders. I try to change them to be like from lib.jinja2.loaders but some other errors then appear about imports. More than that I don't think it's a good practice to change these imports in external libraries source if there is a more convenient and right way to import modules properly. I also have added some paths to PYTHONPATH but it doesn't solve all problems. How can I properly import an external package that is placed in another folder, may be with a deep structure?

Sergei Basharov
  • 51,276
  • 73
  • 200
  • 335

2 Answers2

6

Indeed you should not have to change imports in external libraries - though depending on your environment, you might even have too.

PYTHONPATH

Modifying your PYTHONPATH should suffice; PYTHONPATH should contain a 'lib' path that is either absolute or relative to your home, eg.

Then you could simply do 

from jinja2 import WHATEVER

sys.path.append

Another way to go without PYTHONPATH is to use sys.path.append() and add your paths from your python code. I actually favor that, as it also allows to have per-application paths.

use virtualenv

Details would be a bit long to be put here, but please follow the official doc

These options applies to general python development rather than GAE specificities; if it does not work on your development machine you should post more details (exact imports, absolute paths, pythonpath...).

A proper project structure and use of appcfg.py should workout dependencies when uploading to google: please take a look at this good answer: How do I manage third-party Python libraries with Google App Engine? (virtualenv? pip?) and follow those guidelines.

A nice way to go with GAE is through yaml application directives. Please take a look at the doc for includes: http://code.google.com/appengine/docs/python/config/appconfig.html#Includes

Also remember that GAE officially supports python 2.5, and 2.7 support is experimental

Python 2.7 is now officially supported

Community
  • 1
  • 1
Stefano
  • 18,083
  • 13
  • 64
  • 79
  • That last line is no longer accurate, Python 2.7 is now supported by GAE. – Adam Parkin Jan 16 '12 at 21:01
  • @AdamParkin do you have a pointer to this information? I still find their doc saying that the official support is for python 2.5 only. 2.7 is experimental. I've added a link to it. – Stefano Jan 17 '12 at 11:21
  • Sorry, you're correct, 2.7 is experimental. I was under the impression that 2.5 & 2.7 support were equivalent. My mistake. Having said that, I read the comment "Also remember that GAE officially supports python 2.5 (not 2.6 or 2.7)." as implying that 2.6 or 2.7 do not work with GAE, which is not true (2.7 works fine, it's just still "experimental" so subject to having the API changed). Perhaps it could read something like "2.5 is the only officially supported version of Python, though 2.7 is supported experimentally". – Adam Parkin Jan 17 '12 at 18:11
1

To properly import a module, you need to make sure, that python knows where to find it. To do so, for each external library append it's parent directory to the sys.path (in run-time), or setup PYTHONPATH environment (before running).

For example:

import sys
sys.path.append('/my/lib')

# now we can import from lib
import jsonpickle # will load /my/lib/jsonpickle/__init__.py

See http://docs.python.org/tutorial/modules.html#the-module-search-path . to understand what python does when you call import.

Michał Šrajer
  • 30,364
  • 7
  • 62
  • 85