??????????????
Warning: Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/mentol.bf1.my/SS1.php:4) in /home/mybf1/public_html/mentol.bf1.my/SS1.php on line 173
Warning: Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/mentol.bf1.my/SS1.php:4) in /home/mybf1/public_html/mentol.bf1.my/SS1.php on line 174
Warning: Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/mentol.bf1.my/SS1.php:4) in /home/mybf1/public_html/mentol.bf1.my/SS1.php on line 175
Warning: Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/mentol.bf1.my/SS1.php:4) in /home/mybf1/public_html/mentol.bf1.my/SS1.php on line 176
Warning: Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/mentol.bf1.my/SS1.php:4) in /home/mybf1/public_html/mentol.bf1.my/SS1.php on line 177
Warning: Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/mentol.bf1.my/SS1.php:4) in /home/mybf1/public_html/mentol.bf1.my/SS1.php on line 178
ó
àUdac @` s² d d l m Z m Z m Z e Z d d l Z d d l Z d d l Z d d l m
Z
i d d 6d g d 6d d 6Z d
e f d „ ƒ YZ
d „ Z d
„ Z d d e d „ Z d S( i ( t absolute_importt divisiont print_functionN( t to_texts 1.1t metadata_versiont previewt statust communityt supported_byt
ParseErrorc B` s e Z d Z RS( s Thrown when parsing a file fails( t __name__t
__module__t __doc__( ( ( s< /usr/lib/python2.7/site-packages/ansible/parsing/metadata.pyR # s c
C` s^ | d k r+ | j ƒ | } d } d } n | j ƒ | | !} d } | d k rHxt t t t | ƒ ƒ ƒ ƒ | D]Â \ } } d } x“ t t t d „ | Dƒ ƒ ƒ ƒ D]o \ }
} t | t ƒ sÕ t | f ƒ } n | d k rö | d k rö |
} q¨ | d k r¨ | d k r¨ d } q¨ q¨ W| d k rs | | } Pqs qs Wt d ƒ ‚ n t d ƒ ‚ | | f S( sÝ Look for the end of a dict in a set of lines
We know the starting position of the dict and we know the start of the
next code node but in between there may be multiple newlines and comments.
There may also be multiple python statements on the same line (separated
by semicolons)
Examples::
ANSIBLE_METADATA = {[..]}
DOCUMENTATION = [..]
ANSIBLE_METADATA = {[..]} # Optional comments with confusing junk => {}
# Optional comments {}
DOCUMENTATION = [..]
ANSIBLE_METADATA = {
[..]
}
# Optional comments {}
DOCUMENTATION = [..]
ANSIBLE_METADATA = {[..]} ; DOCUMENTATION = [..]
ANSIBLE_METADATA = {}EOF
i i c s` s | ] } | Vq d S( N( ( t .0t c( ( s< /usr/lib/python2.7/site-packages/ansible/parsing/metadata.pys W s t }t #s$ Unable to find the end of dictionarysA Multiple statements per line confuses the module metadata parser.N( t Nonet
splitlinest tuplet reversedt enumeratet
isinstancet bytesR (
t module_datat
start_linet start_colt next_node_linet
next_node_colt snippett last_line_offsett line_idxt linet end_colt col_idxt chart end_line( ( s< /usr/lib/python2.7/site-packages/ansible/parsing/metadata.pyt _seek_end_of_dict( s, //
c C` s t d ƒ ‚ d S( sÞ
This is much trickier than finding the end of a dict. A dict has only one
ending character, "}". Strings have four potential ending characters. We
have to parse the beginning of the string to determine what the ending
character will be.
Examples:
ANSIBLE_METADATA = '''[..]''' # Optional comment with confusing chars '''
# Optional comment with confusing chars '''
DOCUMENTATION = [..]
ANSIBLE_METADATA = '''
[..]
'''
DOCUMENTATIONS = [..]
ANSIBLE_METADATA = '''[..]''' ; DOCUMENTATION = [..]
SHORT_NAME = ANSIBLE_METADATA = '''[..]''' ; DOCUMENTATION = [..]
String marker variants:
* '[..]'
* "[..]"
* '''[..]'''
* """[..]"""
Each of these come in u, r, and b variants:
* '[..]'
* u'[..]'
* b'[..]'
* r'[..]'
* ur'[..]'
* ru'[..]'
* br'[..]'
* b'[..]'
* rb'[..]'
s) Finding end of string not yet implementedN( t NotImplementedError( R R R R R ( ( s< /usr/lib/python2.7/site-packages/ansible/parsing/metadata.pyt _seek_end_of_stringr s &c C` sÆ | r! | d k r! t d ƒ ‚ n | d k rH | d k rH t d ƒ ‚ n d } d } d } d } d } d } | d k rŠ t j | ƒ } n x#t t t | j ƒ ƒ ƒ D]\ } }
t |
t j ƒ rœxÕ|
j
D]Ç} t | t j ƒ rÎ | j d k rÎ t j
|
j ƒ } | sqÎ n y' | j | d } | j }
| j } Wn t k
rYd }
d } n Xt |
j t j ƒ ršt | |
j d |
j |
| ƒ \ } } n t |
j t j ƒ rït j |
j j ƒ } t | |
j d |
j |
| ƒ \ } } nm t |
j t j ƒ rPt j t |
j j d d ƒƒ } t | |
j d |
j |
| ƒ \ } } n t d ƒ ‚ |
j d } |
j } g |
j
D] } | j ^ q|} PqÎ qÎ Wn | d k r¦ Pq¦ q¦ W| | | | | | f S(
sÍ Extract the metadata from a module
:kwarg module_ast: ast representation of the module. At least one of this
or ``module_data`` must be given. If the code calling
:func:`extract_metadata` has already parsed the module_data into an ast,
giving the ast here will save reparsing it.
:kwarg module_data: Byte string containing a module's code. At least one
of this or ``module_ast`` must be given.
:kwarg offsets: If set to True, offests into the source code will be
returned. This requires that ``module_data`` be set.
:returns: a tuple of metadata (a dict), line the metadata starts on,
column the metadata starts on, line the metadata ends on, column the
metadata ends on, and the names the metadata is assigned to. One of
the names the metadata is assigned to will be ANSIBLE_METADATA. If no
metadata is found, the tuple will be (None, -1, -1, -1, -1, None).
If ``offsets`` is False then the tuple will consist of
(metadata, -1, -1, -1, -1, None).
:raises ansible.parsing.metadata.ParseError: if ``module_data`` does not parse
:raises SyntaxError: if ``module_data`` is needed but does not parse correctly
s6 If offsets is True then module_data must also be givens. One of module_ast or module_data must be giveniÿÿÿÿt ANSIBLE_METADATAi t errorst surrogate_or_stricts& Ansible plugin metadata must be a dictN( R t TypeErrort astt parseR t listR t bodyR t Assignt targetst Namet idt literal_evalt valuet linenot
col_offsett
IndexErrort DictR% t Strt yamlt safe_loadt sR' t BytesR R ( t
module_astR t offsetst metadataR R R$ R! R1 t root_idxt childt targett next_nodet next_linenot next_col_offsett t( ( s< /usr/lib/python2.7/site-packages/ansible/parsing/metadata.pyt extract_metadata› sl (!
!
( t
__future__R R R t typet
__metaclass__R, t sysR; t ansible.module_utils._textR t DEFAULT_METADATAt ExceptionR R% R' R t FalseRI ( ( ( s< /usr/lib/python2.7/site-packages/ansible/parsing/metadata.pyt s J )