ok

Mini Shell

Direktori : /proc/self/root/proc/self/root/proc/self/root/lib/python2.7/site-packages/jinja2/
Upload File :
Current File : //proc/self/root/proc/self/root/proc/self/root/lib/python2.7/site-packages/jinja2/meta.pyc

�
,��Qc@sbdZddlmZddlmZddlmZdefd��YZd�Zd�Z	d	S(
s5
    jinja2.meta
    ~~~~~~~~~~~

    This module implements various functions that exposes information about
    templates that might be interesting for various kinds of applications.

    :copyright: (c) 2010 by the Jinja Team, see AUTHORS for more details.
    :license: BSD, see LICENSE for more details.
i����(tnodes(t
CodeGenerator(tstring_typestTrackingCodeGeneratorcBs)eZdZd�Zd�Zd�ZRS(s.We abuse the code generator for introspection.cCs&tj||dd�t�|_dS(Ns<introspection>(Rt__init__tsettundeclared_identifiers(tselftenvironment((s//usr/lib/python2.7/site-packages/jinja2/meta.pyRscCsdS(sDon't write.N((Rtx((s//usr/lib/python2.7/site-packages/jinja2/meta.pytwritescCs|jj|jj�dS(s$Remember all undeclared identifiers.N(Rtupdatetidentifierst
undeclared(Rtframe((s//usr/lib/python2.7/site-packages/jinja2/meta.pytpull_localss(t__name__t
__module__t__doc__RR
R(((s//usr/lib/python2.7/site-packages/jinja2/meta.pyRs		cCs#t|j�}|j|�|jS(sReturns a set of all variables in the AST that will be looked up from
    the context at runtime.  Because at compile time it's not known which
    variables will be used depending on the path the execution takes at
    runtime, all variables are returned.

    >>> from jinja2 import Environment, meta
    >>> env = Environment()
    >>> ast = env.parse('{% set foo = 42 %}{{ bar + foo }}')
    >>> meta.find_undeclared_variables(ast)
    set(['bar'])

    .. admonition:: Implementation

       Internally the code generator is used for finding undeclared variables.
       This is good to know because the code generator might raise a
       :exc:`TemplateAssertionError` during compilation and as a matter of
       fact this function can currently raise that exception as well.
    (RRtvisitR(tasttcodegen((s//usr/lib/python2.7/site-packages/jinja2/meta.pytfind_undeclared_variables!s
ccsKxD|jtjtjtjtjf�D]}t|jtj�s�t|jtj	tj
f�r�xS|jjD]=}t|tj�r�t|jt
�r�|jVq�qndVqnWq(dVq(nt|jjt
�r�|jjVq(t|tj�r>t|jjttf�r>x3|jjD]}t|t
�r|VqqWq(dVq(WdS(sbFinds all the referenced templates from the AST.  This will return an
    iterator over all the hardcoded template extensions, inclusions and
    imports.  If dynamic inheritance or inclusion is used, `None` will be
    yielded.

    >>> from jinja2 import Environment, meta
    >>> env = Environment()
    >>> ast = env.parse('{% extends "layout.html" %}{% include helper %}')
    >>> list(meta.find_referenced_templates(ast))
    ['layout.html', None]

    This function is useful for dependency tracking.  For example if you want
    to rebuild parts of the website after a layout template has changed.
    N(tfind_allRtExtendst
FromImporttImporttIncludet
isinstancettemplatetConsttTupletListtitemstvalueRtNonettupletlist(Rtnodet
template_name((s//usr/lib/python2.7/site-packages/jinja2/meta.pytfind_referenced_templates9s&N(
Rtjinja2Rtjinja2.compilerRtjinja2._compatRRRR((((s//usr/lib/python2.7/site-packages/jinja2/meta.pyt<module>s	

Zerion Mini Shell 1.0