Edit File: meta.cpython-311.pyc
� ��gh# � �b � d Z ddlmZ ddlmZ ddlmZ ddlmZ G d� de� � Zd� Z d � Z d S ) z_Functions that expose information about templates that might be interesting for introspection. � )�nodes)� iteritems)� string_types)� CodeGeneratorc �$ � e Zd ZdZd� Zd� Zd� ZdS )�TrackingCodeGeneratorz.We abuse the code generator for introspection.c �Z � t j | |dd� � t � � | _ d S )Nz<introspection>)r �__init__�set�undeclared_identifiers)�self� environments �k/builddir/build/BUILD/imunify360-venv-2.6.0/opt/imunify360/venv/lib/python3.11/site-packages/jinja2/meta.pyr z TrackingCodeGenerator.__init__ s- � �� �t�[�2C�EV�W�W�W�&)�e�e��#�#�#� c � � dS )z Don't write.N� )r �xs r �writezTrackingCodeGenerator.write s � � � r c �� � t j | |� � t |j j � � D ]6\ }\ }}|dk r(|| j j vr| j � |� � �7dS )z$Remember all undeclared identifiers.�resolveN) r � enter_framer �symbols�loadsr �globalsr �add)r �frame�_�action�params r r z!TrackingCodeGenerator.enter_frame sw � ��!�$��.�.�.�"+�E�M�,?�"@�"@� 7� 7� �A������"�"�u�D�4D�4L�'L�'L��+�/�/��6�6�6�� 7� 7r N)�__name__� __module__� __qualname__�__doc__r r r r r r r r sG � � � � � �8�8�,� ,� ,�� � �7� 7� 7� 7� 7r r c �b � t | j � � }|� | � � |j S )a 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 �visitr )�ast�codegens r �find_undeclared_variablesr( s. � �& $�C�O�4�4�G� �M�M�#���� � )�)r c # � K � | � t j t j t j t j f� � D �]@}t |j t j � � s�t |j t j t j f� � rR|j j D ]D}t |t j � � r$t |j t � � r |j V � �@dV � �EndV � ��t |j j t � � r|j j V � ��t |t j � � rPt |j j t t f� � r*|j j D ]}t |t � � r|V � � ��<dV � ��BdS )ab 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)�find_allr �Extends� FromImport�Import�Include� isinstance�template�Const�Tuple�List�items�valuer �tuple�list)r& �node� template_names r �find_referenced_templatesr: 5 s� � � � � � � � � ��(�%�,�� �F�� � !� !�� �$�-���5�5� ��$�-�%�+�u�z�)B�C�C� �%)�]�%8� #� #�M� "�-���=�=� #�%�m�&9�<�H�H� 6�"/�"5� 5� 5� 5�� #� � � � �#� � � � � � �d�m�)�<� 8� 8� ��-�%� %� %� %� %� ��e�m� ,� ,� �� �M� �%�� �2 � 2 � � "&� �!4� (� (� � �m�\�:�:� (�'�'�'�'�� (� �J�J�J�J�C!� !r N) r# � r �_compatr r �compilerr r r( r: r r r �<module>r> s� ��� � � � � � � � � � � � � � !� !� !� !� !� !� #� #� #� #� #� #�7� 7� 7� 7� 7�M� 7� 7� 7�$*� *� *�00� 0� 0� 0� 0r
Back to File Manager