jinja2.bccache

module documentation

(source)

The optional bytecode cache system. This is useful if you have very complex template situations and the compilation of all those templates slows down your application too much. Situations where this is useful are often forking web applications that are initialized on the first request.

Class	`Bucket`	Buckets are used to store the bytecode for one template. It's created and initialized by the bytecode cache and passed to the loading functions.
Class	`BytecodeCache`	To implement your own bytecode cache you have to subclass this class and override :meth:`load_bytecode` and :meth:`dump_bytecode`. Both of these methods are passed a :class:`~jinja2.bccache.Bucket`.
Class	`FileSystemBytecodeCache`	A bytecode cache that stores bytecode on the filesystem. It accepts two arguments: The directory where the cache items are stored and a pattern string that is used to build the filename.
Class	`MemcachedBytecodeCache`	This class implements a bytecode cache that uses a memcache cache for storing the information. It does not enforce a specific memcache library (tummy's memcache or cmemcache) but will accept any class that provides the minimal interface required.
Variable	`bc_magic`	Undocumented
Variable	`bc_version`	Undocumented
Class	`_MemcachedClient`	Undocumented

bc_magic = (source)

Undocumented

bc_version: int = (source)

Undocumented