Why Gemfury? Push, build, and install  RubyGems npm packages Python packages Maven artifacts PHP packages Go Modules Debian packages RPM packages NuGet packages

Repository URL to install this package:

Details    
Size: Mime:
B

ÆÕ&†ßTã@sPdZddlZddlZddlmZmZddlmZddd„Z	dd	„Z
d
d
d„ZdS)aCoverage data for coverage.py.

This file had the 4.x JSON data support, which is now gone.  This file still
has storage-agnostic helpers, and is kept to avoid changing too many imports.
CoverageData is now defined in sqldata.py, and imported here to keep the
imports working.

éN)ÚCoverageExceptionÚfile_be_gone)ÚCoverageDataFcCsFi}|rdd„}ntjj}x&| ¡D]}t| |¡ƒ|||ƒ<q$W|S)aHReturn a dict summarizing the line coverage data.

    Keys are based on the file names, and values are the number of executed
    lines.  If `fullpath` is true, then the keys are the full pathnames of
    the files, otherwise they are the basenames of the files.

    Returns a dict mapping file names to counts of lines.

    cSs|S)N©)Úfrrú‹/build/wlanpi-profiler-MIf3Xw/wlanpi-profiler-1.0.8/debian/wlanpi-profiler/opt/wlanpi-profiler/lib/python3.7/site-packages/coverage/data.pyÚ<lambda> ózline_counts.<locals>.<lambda>)ÚosÚpathÚbasenameZmeasured_filesÚlenÚlines)ÚdataÚfullpathZsummZfilename_fnÚfilenamerrrÚline_countss

rcCsN| ¡r"| t| |¡pgƒ¡n| t| |¡p4gƒ¡| | |¡¡dS)zÊContribute `filename`'s data to the `hasher`.

    `hasher` is a `coverage.misc.Hasher` instance to be updated with
    the file's data.  It should only get the results data, not the run
    data.

    N)Zhas_arcsÚupdateÚsortedZarcsrZfile_tracer)rrZhasherrrrÚadd_data_to_hash(srcCs¸tj | ¡¡\}}|d}|p$|g}g}xn|D]f}	tj |	¡rT| tj |	¡¡q0tj |	¡rˆtj tj |	¡|¡}
| 	t
 
|
¡¡q0td|	fƒ‚q0W|rª|sªtdƒ‚d}xð|D]è}|| ¡krä|j
 d¡r´|j
 d|f¡q´|j
 d¡r|j
 d|f¡yt||j
d}
|
 ¡Wn:tk
rX}z|jrH| t|ƒ¡Wd	d	}~XYq´X|j|
|d
|d7}|s´|j
 d¡r”|j
 d|f¡t|ƒq´W|r´|s´td
ƒ‚d	S)a™Combine a number of data files together.

    Treat `data.filename` as a file prefix, and combine the data from all
    of the data files starting with that prefix plus a dot.

    If `aliases` is provided, it's a `PathAliases` object that is used to
    re-map paths to match the local machine's.

    If `data_paths` is provided, it is a list of directories or files to
    combine.  Directories are searched for files that start with
    `data.filename` plus dot as a prefix, and those files are combined.

    If `data_paths` is not provided, then the directory portion of
    `data.filename` is used as the directory to search for data files.

    Unless `keep` is True every data file found and combined is then deleted from disk. If a file
    cannot be read, a warning will be issued, and the file will not be
    deleted.

    If `strict` is true, and no files are found to combine, an error is
    raised.

    z.*z,Couldn't combine from non-existent path '%s'zNo data to combinerZdataiozSkipping combining ourself: %rzCombining data file %r)ÚdebugN)ÚaliasesézDeleting combined data file %rzNo usable data files)r
rÚsplitÚ
base_filenameÚisfileÚappendÚabspathÚisdirÚjoinÚextendÚglobrZ
data_filenameÚ_debugZshouldÚwriterÚreadÚ_warnÚstrrr)rrZ
data_pathsÚstrictZkeepÚdata_dirÚlocalZlocaldotZfiles_to_combineÚpÚpatternZfiles_combinedrZnew_dataÚexcrrrÚcombine_parallel_data7sF


 r-)F)NNFF)Ú__doc__r!Úos.pathr
Z
coverage.miscrrZcoverage.sqldatarrrr-rrrrÚ<module>s