B

ǶZÒ×Ko¨ã@sv
dZd
dl
Z
d
dlZd
dlZd
dlZd
dlZd
dlZd
dlZd
dlZd
dl	m
Z

d
dlmZ
d
dl
mZmZmZmZ
eeƒ
Zdd„Zdd	„Zed
d
dd
„ƒ
Zed
d
dd„ƒ
ZdZed
d
ddd„ƒ
Ze
jràiZiZdd„Zndd„Zed
d
dd„ƒ
Zdd„Zdadaeƒ
dd„Z dd„Z!Gdd „d ƒZ"Gd!d"„d"ƒZ#Gd#d$„d$ƒZ$d%d&„Z%d.d(d)„
Z&Gd*d+„d+ƒZ'd,d-„Z(dS)/zFile wrangling.éN)
Úenv)
ÚConfigError)ÚcontractÚhuman_sortedÚisolate_moduleÚ
join_regexcCs tj
 ttjƒ
tj¡
aiad
S)z?Set the directory that `relative_filename` will be relative to.N)ÚosÚpathÚnormcaseÚabs_fileÚcurdirÚsepÚRELATIVE_DIRÚCANONICAL_FILENAME_CACHE©rrú/build/wlanpi-profiler-7IIg1Q/wlanpi-profiler-1.0.11/debian/wlanpi-profiler/opt/wlanpi-profiler/lib/python3.7/site-packages/coverage/files.pyÚset_relative_directorysrc
CstS)
z=Return the directory that `relative_filename` is relative to.)
rrrrrÚrelative_directory#srÚunicode)
Úreturnsc
Cs*tj
 |¡
}
|
 t¡
r&|ttƒ
d
…}|S)zœReturn the relative form of `filename`.

    The file name will be relative to the current directory when the
    `set_relative_directory` was called.

    N)rr	r
Ú
startswithrÚlen)ÚfilenameZfnormrrrÚrelative_filename(s



rc
	Cs”|tkrŒ|}
t
j |¡
s|xbt
jg
tjD]P}|d
kr6q(t
j ||¡}yt
j |¡
}Wntk
rl


d}YnX|r(|}
Pq(Wt	|
ƒ
}
|
t|<t|S)zzReturn a canonical file name for `filename`.

    An absolute path with no redundant components and normalized case.

    NF)
rrr	ÚisabsrÚsysÚjoinÚexistsÚUnicodeErrorr)rÚcfr	Ú
frrrrÚcanonical_filename6s"
















r!éd)rrc
CsRt 
|¡
\}
}|
r>t d
|
 d¡
¡ ¡dd…}d|›d}nd}|| dd¡S)	a7
A base for a flat file name to correspond to this file.

    Useful for writing files about the code where you want all the files in
    the same directory, but need to differentiate same-named files from
    different directories.

    For example, the file a/b/c.py will return 'd_86bbcbe134d28fd2_c_py'

    Úsha3_256zUTF-8NéZd_Ú
_ÚÚ
.)ÚntpathÚsplitÚhashlibÚnewÚencodeÚ	hexdigestÚreplace)rÚdirnameÚbasenameÚfpÚprefixrrrÚ
flat_rootnameRs



r3c
CsÌ|tkrt|St
j |¡
\}
}|s.|
 ¡}n’|
s8|}nˆt|
ƒ
}
|
tkrRt|
}n0yt
 |
¡
}Wntk
rx


g}YnX|t|
<t
j 	|¡
}x"|D]}t
j 	|¡
|kr”|}Pq”Wt
j 
|
|¡}|t|<|S)
z:Get the actual path of `path`, including the correct case.)Ú_ACTUAL_PATH_CACHErr	r)ÚupperÚactual_pathÚ_ACTUAL_PATH_LIST_CACHEÚlistdirÚ	Exceptionr
r)r	ÚheadÚtailZactpathÚfilesZnormtailr rrrr6ks.




















r6c


Cs|S)
z*The actual path for non-Windows platforms.r)
r	rrrr6Œsc

Cs>ytj
 |¡
}Wntk
r$


YnXtj
 |¡
}t|ƒ
}|S)
z.Return the absolute normalized form of `path`.)rr	ÚrealpathrÚabspathr6)
r	rrrr‘s





rc

Cstj
jrtj |¡
}|S)
z:Return the string as Python would describe this file name.)rZ
PYBEHAVIORZreport_absolute_filesrr	r>)
rrrrÚpython_reported_files

r?c

Cst 
|¡
pt 
|¡
S)
z)Is `filename` an absolute path on any OS?)r(rÚ	posixpath)
rrrrÚisabs_anywhere©srAc
Cs>g}
x4|pgD](}| d
¡
r(|
 
|¡

q|
 
t|ƒ
¡

qW|
S)a"
Prepare the file patterns for use in a `FnmatchMatcher`.

    If a pattern starts with a wildcard, it is used as a pattern
    as-is.  If it does not start with a wildcard, then it is made
    absolute with the current directory.

    If `patterns` is None, an empty list is returned.

    )Ú
*ú
?)rÚappendr)ÚpatternsZpreppedÚ
prrrÚ
prep_patterns®s





rGc@s2eZ
dZd
Zddd„
Zdd„Zdd„Zd	d
„ZdS)
ÚTreeMatcherzøA matcher for files in a tree.

    Construct with a list of paths, either files or directories. Paths match
    with the `match` method if they are one of the files, or if they are
    somewhere in a subtree rooted at one of the directories.

    ÚunknowncCs(t|
ƒ
|_
tttjj|
ƒƒ
|_||_dS)
N)	rÚoriginal_pathsÚlistÚmaprr	r
ÚpathsÚname)ÚselfrMrNrrrÚ__init__És



zTreeMatcher.__init__c

Csd
|j›d|j
›dS)Nz
<TreeMatcher ú
 ú
>)rNrJ)
rOrrrÚ__repr__Îs
zTreeMatcher.__repr__c


Cs|jS)
z4A list of strings for displaying when dumping state.)
rJ)
rOrrrÚinfoÑszTreeMatcher.infocCsLtj
 |
¡
}
x:|jD]0}|
 |¡
r|
|kr.d
S|
t|ƒ
tjkrd
SqWdS)z1Does `fpath` indicate a file in one of our trees?TF)rr	r
rMrrr
)rOÚfpathrFrrrÚmatchÕs





zTreeMatcher.matchN)
rI)Ú__name__Ú
__module__Ú__qualname__Ú__doc__rPrSrTrVrrrrrHÁs


rHc@s2eZ
dZd
Zddd„
Zdd„Zdd„Zd	d
„ZdS)
Ú
ModuleMatcherz A matcher for modules in a tree.rIcCst|
ƒ
|_
||_dS)
N)rKÚmodulesrN)rOZmodule_namesrNrrrrPås


zModuleMatcher.__init__c

Csd
|j›d|j
›dS)Nz<ModuleMatcher rQrR)rNr\)
rOrrrrSés
zModuleMatcher.__repr__c


Cs|jS)
z4A list of strings for displaying when dumping state.)
r\)
rOrrrrTìszModuleMatcher.infocCsF|
sd
Sx8|jD].}|
 
|¡
r|
|kr*dS|
t|ƒ
dkrdSqWd
S)z<Does `module_name` indicate a module in one of our packages?FTr')r\rr)rOÚmodule_nameÚ
mrrrrVðs





zModuleMatcher.matchN)
rI)rWrXrYrZrPrSrTrVrrrrr[ãs



r[c@s2eZ
dZd
Zddd„
Zdd„Zdd„Zd	d
„ZdS)
ÚFnmatchMatcherz)A matcher for files by file name pattern.rIcCs&t|
ƒ
|_
t|j
tjd
|_||_dS)N)
Úcase_insensitive)rKÚpatsÚfnmatches_to_regexrÚWINDOWSÚrerN)rOrarNrrrrP
s



zFnmatchMatcher.__init__c

Csd
|j›d|j
›dS)Nz<FnmatchMatcher rQrR)rNra)
rOrrrrS
s
zFnmatchMatcher.__repr__c


Cs|jS)
z4A list of strings for displaying when dumping state.)
ra)
rOrrrrT

szFnmatchMatcher.infocCs|j 
|
¡
d
k	S)z1Does `fpath` match one of our file name patterns?N)rdrV)rOrUrrrrV
szFnmatchMatcher.matchN)
rI)rWrXrYrZrPrSrTrVrrrrr_
s



r_c
Cs&t 
d
|¡}
|
r|
 d¡
}ntj}|S)z?Find the path separator used in this string, or os.sep if none.z[\\/]r
)rdÚsearchÚgrouprr
)Ú
sZ	sep_matchZthe_seprrrr

s



r
FcCsVd
d„|Dƒ
}dd„|Dƒ
}|r.dd„|Dƒ
}d}|
r@|tj
O}tjt|ƒ
|d}|S)aº
Convert fnmatch patterns to a compiled regex that matches any of them.

    Slashes are always converted to match either slash or backslash, for
    Windows support, even when running elsewhere.

    If `partial` is true, then the pattern will match if the target string
    starts with the pattern. Otherwise, it must match the entire string.

    Returns: a compiled regex object.  Use the .match method to compare target
    strings.

    c
ss|]}
t 
|
¡
V
qdS)
N)ÚfnmatchÚ	translate)Ú.0Úpatternrrrú	<genexpr>*
sz%fnmatches_to_regex.<locals>.<genexpr>c
ss|]}
t 
dd
|
¡V
qdS)z\\?/z[\\\\/]N)rdÚsub)rjÚregexrrrrl-
sc
ss|]}
t 
dd
|
¡V
qdS)z\\Z(\(\?|$)z\1N)rdrm)rjrnrrrrl4
sr
)
Úflags)rdÚ
IGNORECASEÚcompiler)rEr`ÚpartialZregexesroZcompiledrrrrb
s




rbc@s2eZ
dZd
Zddd„
Zdd„Zdd„Zd	d
„ZdS)
ÚPathAliasesa‰
A collection of aliases for paths.

    When combining data files from remote machines, often the paths to source
    code are different, for example, due to OS differences, or because of
    serialized checkouts on continuous integration machines.

    A `PathAliases` object tracks a list of pattern/result pairs, and can
    map a path through those aliases to produce a unified path.

    FcCsg|_|
|_
dS)
N)ÚaliasesÚrelative)rOrurrrrPI
s

zPathAliases.__init__c
Cs>td
|j
›dƒ

x&|jD]\}
}t|
j›d|›ƒ

qWdS)z;Dump the important parts of the PathAliases, for debugging.zAliases (relative=z):z --> N)Úprintrurtrk)rOrnÚresultrrrÚpprintM
s

zPathAliases.pprintcCsšt|
ƒ
}t
|
ƒ
d
kr|
 d¡
}
|
 d¡
r0tdƒ
‚
|
 d¡
sNt|
|ƒ
sNt|
ƒ
}
|
 |¡
s`|
|7}
t|
g
ddd}t|ƒ
}| d¡
|}|j	 
||f¡

dS)a
Add the `pattern`/`result` pair to the list of aliases.

        `pattern` is an `fnmatch`-style pattern.  `result` is a simple
        string.  When mapping paths, if a path starts with a match against
        `pattern`, then that match is replaced with `result`.  This models
        isomorphic source trees being rooted at different places on two
        different machines.

        `pattern` can't end with a wildcard component, since that would
        match an entire tree, and not just its root.

        é
z\/rBz$Pattern must not end with wildcards.T)r`rrN)r
rÚrstripÚendswithrrrArrbrtrD)rOrkrwZpattern_seprnZ
result_seprrrÚaddS
s











zPathAliases.addcCs^xX|jD]N\}}| 
|
¡
}|r|
 | d
¡
|¡}| t|
ƒ
t|ƒ
¡}|jsRt|ƒ
}|SqW|
S)a?Map `path` through the aliases.

        `path` is checked against all of the patterns.  The first pattern to
        match is used to replace the root of the path with the result root.
        Only one pattern is ever used.  If no patterns match, `path` is
        returned unchanged.

        The separator style in the result is made to match that of the result
        in the alias.

        Returns the mapped path.  If a mapping has happened, this is a
        canonical path.  If no mapping has happened, it is the original value
        of `path` unchanged.

        r
)rtrVr.rfr
rur!)rOr	rnrwr^r+rrrrLy
s








zPathAliases.mapN)
F)rWrXrYrZrPrxr|rLrrrrrs>
s



&rsc
cslxftt
 |¡
ƒ
D]T\}
\}}}|
d
kr:d|kr:|dd…=qx(|D] }t d|¡r@t
j ||¡V
q@WqWdS)a™
Yield all of the importable Python files in `dirname`, recursively.

    To be importable, the files have to be in a directory with a __init__.py,
    except for `dirname` itself, which isn't required to have one.  The
    assumption is that `dirname` was specified directly, so the user knows
    best, but sub-directories are checked for a __init__.py to be sure we only
    find the importable files.

    r
z__init__.pyNz^[^.#~!$@%^&*()+=,]+\.pyw?$)Ú	enumeraterÚwalkrdrVr	r)r/Ú
iÚdirpathÚdirnamesÚ	filenamesrrrrÚfind_python_files”
s






rƒ)FF))rZr*rhr(rÚos.pathr@rdrZcoveragerZcoverage.exceptionsrZ
coverage.miscrrrrrrrr!ZMAX_FLATr3rcr4r7r6rr?rrrArGrHr[r_r
rbrsrƒrrrrÚ<module>sJ










!

"

!V