??
You're inside public_html, but wp-admin or wp-content was not found.
Savvy
W
olf -
MANAGER
Edit File: meta.pyo
� ��_Yc @ sh d Z d d l m Z d d l m Z d d l m Z m Z d e f d � � YZ d � Z d � 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) 2017 by the Jinja Team, see AUTHORS for more details. :license: BSD, see LICENSE for more details. i����( t nodes( t CodeGenerator( t string_typest iteritemst TrackingCodeGeneratorc B s) e Z d Z d � Z d � Z d � Z RS( s. We abuse the code generator for introspection.c C s& t j | | d d � t � | _ d S( Ns <introspection>( R t __init__t sett undeclared_identifiers( t selft environment( ( s/ /usr/lib/python2.7/site-packages/jinja2/meta.pyR s c C s d S( s Don't write.N( ( R t x( ( s/ /usr/lib/python2.7/site-packages/jinja2/meta.pyt write t c C s\ t j | | � xE t | j j � D]1 \ } \ } } | d k r# | j j | � q# q# Wd S( s$ Remember all undeclared identifiers.t resolveN( R t enter_frameR t symbolst loadsR t add( R t framet _t actiont param( ( s/ /usr/lib/python2.7/site-packages/jinja2/meta.pyR s % ( t __name__t __module__t __doc__R R R ( ( ( s/ /usr/lib/python2.7/site-packages/jinja2/meta.pyR s c C s# t | j � } | j | � | j S( s Returns 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']) True .. 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. ( R R t visitR ( t astt codegen( ( s/ /usr/lib/python2.7/site-packages/jinja2/meta.pyt find_undeclared_variables$ s c c sK xD| j t j t j t j t j f � D]} t | j t j � s� t | j t j t j f � r� xS | j j D]= } t | t j � r� t | j t � r� | j Vq� qn d Vqn Wq( d Vq( n t | j j t � r� | j j Vq( t | t j � r>t | j j t t f � r>x3 | j j D] } t | t � r| VqqWq( d Vq( Wd S( sb Finds 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( t find_allR t Extendst FromImportt Importt Includet isinstancet templatet Constt Tuplet Listt itemst valueR t Nonet tuplet list( R t nodet template_name( ( s/ /usr/lib/python2.7/site-packages/jinja2/meta.pyt find_referenced_templates< s& N( R t jinja2R t jinja2.compilerR t jinja2._compatR R R R R. ( ( ( s/ /usr/lib/python2.7/site-packages/jinja2/meta.pyt <module> s
SavvyWolf - MANAGER