HTML embedded in code is messy and difficult to maintain. It's better to use a templating system, where the HTML is kept in a separate file with special syntax to indicate where the data from the application appears. There are many templating systems for Python: EZT, Cheetah, ClearSilver, Quixote, Django, and Jinja2 are just a few. You can use your template engine of choice by bundling it with your application code.
For your convenience, App Engine includes the Django and Jinja2 templating engines.
Using Jinja2 Templates
First modify the
libraries section at the bottom of
This configuration makes the newest supported version of Jinja2 available to your application. To avoid possible compatibility issues, serious applications should use an actual version number rather than
Now modify the statements at the top of
MainPage handler with code that resembles the following:
Finally, create a new file in the
guestbook directory named
index.html, with the following contents:
Reload the page, and try it out.
JINJA_ENVIRONMENT.get_template(name) takes the name of a template file, and returns a template object.
template.render(template_values) takes a dictionary of values, and returns the rendered text. The template uses Jinja2 templating syntax to access and iterate over the values, and can refer to properties of those values. In many cases, you can pass datastore model objects directly as values, and access their properties from templates.
Tip: An App Engine application has read-only access to all of the files uploaded with the project, the library modules, and no other files. The current working directory is the application root directory, so the path to
index.html is simply
Other templating languages
This example was done in Jinja2, but we also have App Engine starter projects that use Flask and Bottle in the Google Developers Console.