0  891_I|Mdv &K Index of /wp-content/themes/salient/sym404/root/sys/bus/node/devices/node0/memory21/subsystem/drivers

Index of /wp-content/themes/salient/sym404/root/sys/bus/node/devices/node0/memory21/subsystem/drivers

 NameLast modifiedSizeDescription
 Parent Directory   -  
 355_I|Mjq؂ 404 Not Found

Not Found

The requested URL was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

  355c 404 Not Found

Not Found

The requested URL was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

, lae\\i1h _I|? API === .. module:: jinja2 :synopsis: public Jinja2 API This document describes the API to Jinja2 and not the template language. It will be most useful as reference to those implementing the template interface to the application and not those who are creating Jinja2 templates. Basics ------ Jinja2 uses a central object called the template :class:`Environment`. Instances of this class are used to store the configuration, global objects and are used to load templates from the file system or other locations. Even if you are creating templates from strings by using the constructor of :class:`Template` class, an environment is created automatically for you, albeit a shared one. Most applications will create one :class:`Environment` object on application initialization and use that to load templates. In some cases it's however useful to have multiple environments side by side, if different configurations are in use. The simplest way to configure Jinja2 to load templates for your application looks roughly like this:: from jinja2 import Environment, PackageLoader env = Environment(loader=PackageLoader('yourapplication', 'templates')) This will create a template environment with the default settings and a loader that looks up the templates in the `templates` folder inside the `yourapplication` python package. Different loaders are available and you can also write your own if you want to load templates from a database or other resources. To load a template from this environment you just have to call the :meth:`get_template` method which then returns the loaded :class:`Template`:: template = env.get_template('mytemplate.html') To render it with some variables, just call the :meth:`render` method:: print template.render(the='variables', go='here') Using a template loader rather then passing strings to :class:`Template` or :meth:`Environment.from_string` has multiple advantages. Besides being a lot easier to use it also enables template inheritance. Unicode ------- Jinja2 is using Unicode internally which means that you have to pass Unicode objects to the render function or bytestrings that only consist of ASCII characters. Additionally newlines are normalized to one end of line sequence which is per default UNIX style (``\n``). Pytho