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

dfinimundi / wlanpi-profiler deb

Repository URL to install this package:

Version: 
1.0.11  ▾
Details    
wlanpi-profiler / opt / wlanpi-profiler / lib / python3.7 / site-packages / coverage / __pycache__ / control.cpython-37.pyc
Size: Mime: 
B

‹õF¢óŸã@s<dZddlZddlZddlZddlZddlZddlZddlZddlZddl	Z	ddl
mZddlm
Z
ddlmZmZddlmZddlmZmZddlmZmZdd	lmZmZmZdd
lmZddlm Z m!Z!m"Z"m#Z#ddl$m%Z%m&Z&m'Z'm(Z(dd
l)m*Z*ddl+m,Z,ddl-m.Z.ddl/m0Z0m1Z1m2Z2m3Z3ddl/m4Z4m5Z5m6Z6ddl7m8Z8ddl9m:Z:ddl;m<Z<ddl=m>Z>ddl?m@Z@ddlAmBZBddlCmDZDyddlEmFZFWneGk
r¾dZFYnXe6eƒZejHdd„ƒZIe4dƒZJGdd„dƒZKeLejM Ndd¡ƒr(dd lmOZOmPZPeOePd!d"d#gd$eKƒZKd%d&„ZQd'd(„ZRdS))z#Core control stuff for coverage.py.éN)Úenv)ÚAnnotateReporter)Ú	CollectorÚCTracer)Úread_coverage_config)Ú"should_start_context_test_functionÚcombine_context_switchers)ÚCoverageDataÚcombine_parallel_data)ÚDebugControlÚshort_stackÚwrite_formatted_info)Údisposition_debug_msg)ÚConfigErrorÚCoverageExceptionÚCoverageWarningÚPluginError)ÚPathAliasesÚabs_fileÚrelative_filenameÚset_relative_directory)ÚHtmlReporter)ÚInOrOut)ÚJsonReporter)Úbool_or_noneÚ
join_regexÚhuman_sortedÚhuman_sorted_items)ÚDefaultValueÚensure_dir_for_fileÚisolate_module)ÚFileReporter)ÚPlugins)ÚPythonFileReporter)Ú
render_report)ÚAnalysis)ÚSummaryReporter)ÚXmlReporter)Úpatch_multiprocessingcks8|j}|j ¡|_z|jjf|ŽdVWd||_XdS)zÇTemporarily tweak the configuration of `cov`.

    The arguments are applied to `cov.config` with the `from_args` method.
    At the end of the with-statement, the old configuration is restored.
    N)ÚconfigÚcopyZ	from_args)ÚcovÚkwargsZoriginal_config©r-ú/build/wlanpi-profiler-7IIg1Q/wlanpi-profiler-1.0.11/debian/wlanpi-profiler/opt/wlanpi-profiler/lib/python3.7/site-packages/coverage/control.pyÚoverride_config/s
r/ÚMISSINGc@sˆeZdZdZgZedd„ƒZedddddddddddddddfdd„Zd	d
„Z	dd„Z
d
d„Zdd„Zdd„Z
dTdd„Zdd„Zdd„Zdd„Zdd„Zdd„Zdd „Zd!d"„Zd#d$„Zd%d&„Zd'd(„Zd)d*„ZdUd,d-„ZdVd.d/„Zd0d1„Zd2d3„ZdWd4d5„Zd6d7„ZdXd8d9„Z d:d;„Z!d<d=„Z"d>d?„Z#d@dA„Z$dBdC„Z%dDdE„Z&dYdFdG„Z'dZdHdI„Z(d[dJdK„Z)d\dLdM„Z*d]dNdO„Z+d^dPdQ„Z,dRdS„Z-dS)_ÚCoverageaProgrammatic access to coverage.py.

    To use::

        from coverage import Coverage

        cov = Coverage()
        cov.start()
        #.. call your code ..
        cov.stop()
        cov.html_report(directory='covhtml')

    Note: in keeping with Python custom, names starting with underscore are
    not part of the public API. They might stop working at any point.  Please
    limit yourself to documented methods to avoid problems.

    Methods can raise any of the exceptions described in :ref:`api_exceptions`.

    cCs|jr|jdSdSdS)zŽGet the latest started `Coverage` instance, if any.

        Returns: a `Coverage` instance, or None.

        .. versionadded:: 5.0

        éÿÿÿÿN)Ú
_instances)Úclsr-r-r.ÚcurrentYs	
zCoverage.currentNFTcCsæ|dk|_|tkrd}d|_d|_||_|_||_d|_d|_||_	d|_
||_g|_d|_
|_d|_d|_d|_|_d|_d|_d|_d|_d|_d|_d|_t||j||||t|ƒ||	|
|||
||
|d|_tjsâtƒdS)aÿ
        Many of these arguments duplicate and override values that can be
        provided in a configuration file.  Parameters that are missing here
        will use values from the config file.

        `data_file` is the base name of the data file to use. The config value
        defaults to ".coverage".  None can be provided to prevent writing a data
        file.  `data_suffix` is appended (with a dot) to `data_file` to create
        the final file name.  If `data_suffix` is simply True, then a suffix is
        created with the machine and process identity included.

        `cover_pylib` is a boolean determining whether Python code installed
        with the Python interpreter is measured.  This includes the Python
        standard library and any packages installed with the interpreter.

        If `auto_data` is true, then any existing data file will be read when
        coverage measurement starts, and data will be saved automatically when
        measurement stops.

        If `timid` is true, then a slower and simpler trace function will be
        used.  This is important for some environments where manipulation of
        tracing functions breaks the faster trace function.

        If `branch` is true, then branch coverage will be measured in addition
        to the usual statement coverage.

        `config_file` determines what configuration file to read:

            * If it is ".coveragerc", it is interpreted as if it were True,
              for backward compatibility.

            * If it is a string, it is the name of the file to read.  If the
              file can't be read, it is an error.

            * If it is True, then a few standard files names are tried
              (".coveragerc", "setup.cfg", "tox.ini").  It is not an error for
              these files to not be found.

            * If it is False, then no configuration file is read.

        `source` is a list of file paths or package names.  Only code located
        in the trees indicated by the file paths or package names will be
        measured.

        `source_pkgs` is a list of package names. It works the same as
        `source`, but can be used to name packages where the name can also be
        interpreted as a file path.

        `include` and `omit` are lists of file name patterns. Files that match
        `include` will be measured, files that match `omit` will not.  Each
        will also accept a single string argument.

        `debug` is a list of strings indicating what debugging information is
        desired.

        `concurrency` is a string indicating the concurrency library being used
        in the measured code.  Without this, coverage.py will get incorrect
        results if these libraries are in use.  Valid strings are "greenlet",
        "eventlet", "gevent", "multiprocessing", or "thread" (the default).
        This can also be a list of these strings.

        If `check_preimported` is true, then when coverage is started, the
        already-imported files will be checked to see if they should be
        measured by coverage.  Importing measured files before coverage is
        started can mean that code is missed.

        `context` is a string to use as the :ref:`static context
        <static_contexts>` label for collected data.

        If `messages` is true, some messages will be printed to stdout
        indicating what is happening.

        .. versionadded:: 4.0
            The `concurrency` parameter.

        .. versionadded:: 4.2
            The `concurrency` parameter can now be a list of strings.

        .. versionadded:: 5.0
            The `check_preimported` and `context` parameters.

        .. versionadded:: 5.3
            The `source_pkgs` parameter.

        .. versionadded:: 6.0
            The `messages` parameter.

        NTF)Úconfig_fileÚwarnÚ	data_fileÚcover_pylibÚtimidÚbranchÚparallelÚsourceÚsource_pkgsZrun_omitZrun_includeÚdebugÚreport_omitÚreport_includeÚconcurrencyÚcontext) Ú_no_diskÚ_DEFAULT_DATAFILEr)Ú_debug_fileÚ
_auto_loadÚ
_auto_saveÚ_data_suffix_specifiedÚ
_warn_no_dataÚ_warn_unimported_sourceÚ_warn_preimported_sourceÚ_no_warn_slugsÚ	_messagesÚ	_warningsÚ_dataÚ
_collectorÚ_pluginsÚ_inoroutZ_data_suffixZ_run_suffixÚ_exclude_reÚ_debugÚ_file_mapperÚ_initedÚ_inited_for_startÚ_startedÚ_should_write_debugrÚ_warnrrZMETACOVÚ _prevent_sub_process_measurement)Úselfr8Zdata_suffixr9Z	auto_datar:r;r6r=r>ÚomitÚincluder?rBZcheck_preimportedrCÚmessagesr-r-r.Ú__init__gsBa

zCoverage.__init__cCs¦|jr
dSd|_t|jj|jƒ|_d|jjp.dkr:d|j_i|_t	ƒ|jj
rRtnt|_
t |jj|j|j¡|_x0|jjD]$}| ||jgtt ¡ƒd¡qzWdS)zßSet all the initial state.

        This is called by the public methods to initialize state. This lets us
        construct a :class:`Coverage` object, then tweak its state before this
        function is called.

        NTÚmultiprocessingr-é)rWrr)r?rFrUrBr<rTrÚrelative_filesrrrVr"Zload_pluginsÚpluginsrRÚconfigurersÚ	configureÚintÚtime)r]Úpluginr-r-r.Ú_initszCoverage._initcCsD|jrd|_| ¡|jjr@|jjtddkr@td|jj›ƒ‚dS)z,Stuff to do after everything is initialized.Fé)ÚlimitzCrashing because called by N)rZÚ_write_startup_debugr)Z_crashrÚ	Exception)r]r-r-r.Ú
_post_init*s
zCoverage._post_initc	Cs¾d}|j ¡”|j d¡rLt|jj ¡ƒ}dd„|Dƒ}t|jd|ƒd}|j d¡ržt|jd| ¡ƒx.|j	D]$}d|j
}| ¡}t|j||ƒqrWd}WdQRX|rºt|jd	d
ƒdS)z*Write out debug info at startup if needed.Fr)cSs"g|]\}}| d¡s||f‘qS)Ú_)Ú
startswith)Ú.0ÚkÚvr-r-r.ú
<listcomp>;sz1Coverage._write_startup_debug.<locals>.<listcomp>TÚsyszsys: NÚendr-)rUZwithout_callersÚshouldrr)Ú__dict__Úitemsr
Úsys_inforRÚ_coverage_plugin_name)r]Z	wrote_anyZconfig_inforjÚheaderÚinfor-r-r.rn5s 
zCoverage._write_startup_debugcCs.|j ||¡}|j d¡r*|j t|ƒ¡|S)z„Decide whether to trace execution in `filename`.

        Calls `_should_trace_internal`, and returns the FileDisposition.

        Útrace)rSÚshould_tracerUryÚwriter)r]ÚfilenameÚframeZdispr-r-r.Ú
_should_traceJszCoverage._should_tracecCsL|j ||¡}|j d¡rF|s*d|›}nd|›d|›}|j |¡|S)z˜Check a file name against the include/omit/etc, rules, verbosely.

        Returns a boolean: True if the file should be traced, False if not.

        r€z
Including zNot including z: )rSZcheck_include_omit_etcrUryr‚)r]rƒr„ÚreasonÚmsgr-r-r.Ú_check_include_omit_etcUsz Coverage._check_include_omit_etccCs¨|jdkr"|jdk	r"t|jjƒ|_|jdk	r:||jkr:dS|j |¡|rZ|›d|›d}|jdk	r„|j d¡r„dt 	¡›d|›}t
j|tdd|r¤|j |¡dS)	zºUse `msg` as a warning.

        For warning suppression, use `slug` as the shorthand.

        If `once` is true, only show this warning once (determined by the
        slug.)

        Nz (ú)Úpidú[z] rc)ÚcategoryÚ
stacklevel)
rMr)ÚlistÚdisable_warningsrOÚappendrUryÚosÚgetpidÚwarningsr7r)r]r‡ÚslugÚoncer-r-r.r[es	



zCoverage._warncCs|jrt|ƒdS)z4Write a message to the user, if configured to do so.N)rNÚprint)r]r‡r-r-r.Ú_messageszCoverage._messagecCs|j |¡S)aGet an option from the configuration.

        `option_name` is a colon-separated string indicating the section and
        option name.  For example, the ``branch`` option in the ``[run]``
        section of the config file would be indicated with `"run:branch"`.

        Returns the value of the option.  The type depends on the option
        selected.

        As a special case, an `option_name` of ``"paths"`` will return an
        OrderedDict with the entire ``[paths]`` section value.

        .. versionadded:: 4.0

        )r)Ú
get_option)r]Úoption_namer-r-r.r˜†szCoverage.get_optioncCs|j ||¡dS)a/Set an option in the configuration.

        `option_name` is a colon-separated string indicating the section and
        option name.  For example, the ``branch`` option in the ``[run]``
        section of the config file would be indicated with ``"run:branch"``.

        `value` is the new value for the option.  This should be an
        appropriate Python value.  For example, use True for booleans, not the
        string ``"True"``.

        As an example, calling::

            cov.set_option("run:branch", True)

        has the same effect as this configuration file::

            [run]
            branch = True

        As a special case, an `option_name` of ``"paths"`` will replace the
        entire ``[paths]`` section.  The value should be an OrderedDict.

        .. versionadded:: 4.0

        N)r)Ú
set_option)r]r™Úvaluer-r-r.rš˜szCoverage.set_optioncCs\| ¡|jr|j ¡|jjo0tj |jj¡}|sB|j	dd| 
¡|sX|j ¡dS)z;Load previously-collected coverage data from the data file.N)Úsuffix)
rkrQÚresetr)r<r‘ÚpathÚexistsr8Ú
_init_datarprPÚread)r]Úshould_skipr-r-r.Úload´s
z
Coverage.loadc
CsÎ|jjp
g}d|kr.ts tdƒ‚t|jjd|jj}|rB|dkrHg}n|dkrXtg}ntd|›ƒ‚| dd„|jj	Dƒ¡t
|ƒ}t|j|j
||j|jj|jj|j|d	|_|j}|rÊt|tƒsød
}n.|jjrô|dkràd
}qøt|tƒsøt|ƒ}nd}| |¡|j |j|jj¡|jjrp|jjsp| d d
 dd„|jjDƒ¡|j  ¡¡¡x|jjD]}d|_!q`Wt"|j|j# $d¡rŠ|j#ndd|_%|j% &|j¡|j|j%_'|jj(|j%_)d
|_*t+ ,|j-¡dS)zInitialization for start()rbz/multiprocessing is not supported on this Python)ZrcfileÚnoneZ
test_functionz*Don't understand dynamic_context setting: css|]}|jVqdS)N)Údynamic_context)rsrjr-r-r.ú	<genexpr>Ôsz+Coverage._init_for_start.<locals>.<genexpr>)rZ
check_includeÚshould_start_contextZfile_mapperr:r;r7rBTNz1Plugin file tracers ({}) aren't supported with {}z, css|]}|jVqdS)N)r})rsrjr-r-r.r¦úsFr€)r7r?).r)rBr(rr6r¥rÚextendrRÚcontext_switchersrrr…rˆrVr:r;r[rQrIÚ
isinstanceÚstrr<Úboolr Zuse_datarPrCÚfile_tracersZsupports_pluginsÚformatÚjoinÚtracer_nameÚ_coverage_enabledrrUryrSrgreZfile_disposition_classZ
disp_classrZÚatexitÚregisterÚ_atexit)r]rBZdyconr©r§rœrjr-r-r.Ú_init_for_startÀsj





zCoverage._init_for_startcCs8|jdkr4t|jjƒt|jj||j|j|jd|_dS)z,Create a data file if we don't have one yet.N)Úbasenamerœr7r?Zno_disk)rPrr)r8r	r[rUrD)r]rœr-r-r.r s
zCoverage._init_datacCsl| ¡|jsd|_| ¡| ¡|j ¡|jr>|j ¡|jrL| 	¡|j
 ¡d|_|j
 |¡dS)aaStart measuring code coverage.

        Coverage measurement only occurs in functions called after
        :meth:`start` is invoked.  Statements in the same scope as
        :meth:`start` won't be measured.

        Once you invoke :meth:`start`, you must also call :meth:`stop`
        eventually, or your process might not shut down cleanly.

        TN)rkrXrµrprSZwarn_conflicting_settingsrLZwarn_already_imported_filesrGr£rQÚstartrYr3r)r]r-r-r.r· s


zCoverage.startcCs8|jr|jd|kr|j ¡|jr.|j ¡d|_dS)zStop measuring code coverage.r2FN)r3ÚpoprYrQÚstop)r]r-r-r.r¹@s

z
Coverage.stopcCsH|j d¡r(|j dt ¡›d|›¡|jr6| ¡|jrD| ¡dS)zClean up on process shutdown.Úprocessz
atexit: pid: z, instance: N)	rUryr‚r‘r’rYr¹rHÚsave)r]r-r-r.r´IszCoverage._atexitcCsN| ¡| ¡|jr |j ¡|jdd|jj|jjdd|_d|_	dS)z£Erase previously collected coverage data.

        This removes the in-memory data collected in this session as well as
        discarding the data file.

        N)rœ)r<F)
rkrprQrr rPÚeraser)r<rX)r]r-r-r.r¼Rs
zCoverage.erasecCs6|jstdƒ‚|jjr&|jdddd|j |¡dS)ašSwitch to a new dynamic context.

        `new_context` is a string to use as the :ref:`dynamic context
        <dynamic_contexts>` label for collected data.  If a :ref:`static
        context <static_contexts>` is in use, the static and dynamic context
        labels will be joined together with a pipe character.

        Coverage collection must be started already.

        .. versionadded:: 5.0

        z.Cannot switch context, coverage is not startedzConflicting dynamic contextszdynamic-conflictT)r”r•N)rYrrQr§r[Úswitch_context)r]Znew_contextr-r-r.r½bs

zCoverage.switch_contextÚexcludecCs&| ¡t|j|dgƒ| ¡dS)zClear the exclude list.Ú_listN)rkÚsetattrr)Ú_exclude_regex_stale)r]Úwhichr-r-r.Ú
clear_excludewszCoverage.clear_excludecCs.| ¡t|j|dƒ}| |¡| ¡dS)a|Exclude source lines from execution consideration.

        A number of lists of regular expressions are maintained.  Each list
        selects lines that are treated differently during reporting.

        `which` determines which list is modified.  The "exclude" list selects
        lines that are not considered executable at all.  The "partial" list
        indicates lines with branches that are not taken.

        `regex` is a regular expression.  The regex is added to the specified
        list.  If any of the regexes in the list is found in a line, the line
        is marked for special treatment during reporting.

        r¿N)rkÚgetattrr)rrÁ)r]ÚregexrÂÚ	excl_listr-r-r.r¾}s
zCoverage.excludecCs|j ¡dS)z=Drop all the compiled exclusion regexes, a list was modified.N)rTÚclear)r]r-r-r.rÁ‘szCoverage._exclude_regex_stalecCs2||jkr(t|j|dƒ}t|ƒ|j|<|j|S)z5Return a compiled regex for the given exclusion list.r¿)rTrÄr)r)r]rÂrÆr-r-r.Ú_exclude_regex•s
zCoverage._exclude_regexcCs| ¡t|j|dƒS)z·Return a list of excluded regex patterns.

        `which` indicates which list is desired.  See :meth:`exclude` for the
        lists that are available, and their meaning.

        r¿)rkrÄr))r]rÂr-r-r.Úget_exclude_listœszCoverage.get_exclude_listcCs| ¡}| ¡dS)z2Save the collected coverage data to the data file.N)Úget_datar‚)r]Údatar-r-r.r»¦sz
Coverage.savecCsš| ¡|jdd| ¡| ¡d}|jjr~t|jjd}x>|jj ¡D].}|d}x |dd…D]}| 	||¡qfWqLWt
|j|||||jddS)ašCombine together a number of similarly-named coverage data files.

        All coverage data files whose name starts with `data_file` (from the
        coverage() constructor) will be read, and combined together into the
        current measurements.

        `data_paths` is a list of files or directories from which data should
        be combined. If no list is passed, then the data files from the
        directory indicated by the current data file (probably the current
        directory) will be combined.

        If `strict` is true, then it is an error to attempt to combine when
        there are no data files to combine.

        If `keep` is true, then original input data files won't be deleted.

        .. versionadded:: 4.0
            The `data_paths` parameter.

        .. versionadded:: 4.3
            The `strict` parameter.

        .. versionadded: 5.5
            The `keep` parameter.
        N)rœ)Úrelativeré)ÚaliasesÚ
data_pathsÚstrictÚkeepÚmessage)
rkr rprÊr)ÚpathsrrdÚvaluesÚaddr
rPr—)r]rÏrÐrÑrÎrÓÚresultÚpatternr-r-r.Úcombine«s$zCoverage.combinecCs\| ¡|jdd| ¡x |jD]}|js$|j |¡q$W|jrV|j ¡rV| ¡|j	S)zËGet the collected data.

        Also warn about various problems collecting data.

        Returns a :class:`coverage.CoverageData`, the collected coverage data.

        .. versionadded:: 4.0

        N)rœ)
rkr rprRr±rQZplugin_was_disabledZ
flush_dataÚ_post_save_workrP)r]rjr-r-r.rÊÛs
zCoverage.get_datacCs¨|jr|j ¡|js*|jr*|jddd|jdk	r’t t¡}x.|j 	¡D] \}}| 
|¡}|| |¡qJWx"| ¡D]\}}|j 
||¡qxW|jjr¤| d¡dS)z£After saving data, look for warnings, post-work, etc.

        Warn about things that should have happened but didn't.
        Look for unexecuted files.

        zNo data was collected.zno-data-collected)r”Nz0The '[run] note' setting is no longer supported.)rKrSZwarn_unimported_sourcerPrJr[ÚcollectionsÚdefaultdictrŽZfind_possibly_unexecuted_filesrVrr{Ztouch_filesr)Znote)r]Ú
file_pathsÚ	file_pathÚplugin_namerÓr-r-r.rÙòs	



zCoverage._post_save_workcCs | |¡\}}}}}||||fS)z:Like `analysis2` but doesn't return excluded line numbers.)Ú	analysis2)r]ÚmorfÚfÚsrqÚmZmfr-r-r.ÚanalysisszCoverage.analysiscCs0| |¡}|jt|jƒt|jƒt|jƒ| ¡fS)aGAnalyze a module.

        `morf` is a module or a file name.  It will be analyzed to determine
        its coverage statistics.  The return value is a 5-tuple:

        * The file name for the module.
        * A list of line numbers of executable statements.
        * A list of line numbers of excluded statements.
        * A list of line numbers of statements not run (missing from
          execution).
        * A readable formatted string of the missing line numbers.

        The analysis uses the source file itself and the current measured
        coverage data.

        )Ú_analyzerƒÚsortedZ
statementsZexcludedÚmissingZmissing_formatted)r]ràrär-r-r.rßs
zCoverage.analysis2cCs@| ¡| ¡| ¡}t|tƒs,| |¡}t||jj||j	ƒS)zTAnalyze a single morf or code unit.

        Returns an `Analysis` object.

        )
rkrprÊrªr!Ú_get_file_reporterr%r)Ú	precisionrV)r]ÚitrËr-r-r.rå/s

zCoverage._analyzecCsvd}d}t|tƒr`| |¡}|j |¡}|r`|j |¡}|r`| |¡}|dkr`td 	|j
|¡ƒ‚|dkrrt||ƒ}|S)z-Get a FileReporter for a module or file name.NÚpythonz5Plugin {!r} did not provide a file reporter for {!r}.)rªr«rVrPZfile_tracerrRÚgetÚ
file_reporterrr®r}r#)r]ràrjríZmapped_morfrÞr-r-r.rè?s 



zCoverage._get_file_reportercs:|sˆj ¡}t|tttfƒs$|g}‡fdd„|Dƒ}|S)aGet a list of FileReporters for a list of modules or file names.

        For each module or file name in `morfs`, find a FileReporter.  Return
        the list of FileReporters.

        If `morfs` is a single module or file name, this returns a list of one
        FileReporter.  If `morfs` is empty or None, then the list of all files
        measured is used to find the FileReporters.

        csg|]}ˆ |¡‘qSr-)rè)rsrà)r]r-r.rvjsz0Coverage._get_file_reporters.<locals>.<listcomp>)rPZmeasured_filesrªrŽÚtupleÚset)r]ÚmorfsZfile_reportersr-)r]r.Ú_get_file_reportersXs
zCoverage._get_file_reportersc
Cs>t||||||||	|
|d
t|ƒ}|j||dSQRXdS)aTWrite a textual summary report to `file`.

        Each module in `morfs` is listed, with counts of statements, executed
        statements, missing statements, and a list of lines missed.

        If `show_missing` is true, then details of which lines or branches are
        missing will be included in the report.  If `ignore_errors` is true,
        then a failure while reporting a single file will not stop the entire
        report.

        `file` is a file-like object, suitable for writing.

        `include` is a list of file name patterns.  Files that match will be
        included in the report. Files matching `omit` will not be included in
        the report.

        If `skip_covered` is true, don't report on files with 100% coverage.

        If `skip_empty` is true, don't report on empty files (those that have
        no statements).

        `contexts` is a list of regular expressions.  Only data from
        :ref:`dynamic contexts <dynamic_contexts>` that match one of those
        expressions (using :func:`re.search <python:re.search>`) will be
        included in the report.

        `precision` is the number of digits to display after the decimal
        point for percentages.

        All of the arguments default to the settings read from the
        :ref:`configuration file <config>`.

        Returns a float, the total percentage covered.

        .. versionadded:: 4.0
            The `skip_covered` parameter.

        .. versionadded:: 5.0
            The `contexts` and `skip_empty` parameters.

        .. versionadded:: 5.2
            The `precision` parameter.

        )	Ú
ignore_errorsr@rAÚshow_missingÚskip_coveredÚreport_contextsÚ
skip_emptyréÚsort)ÚoutfileN)r/r&Úreport)
r]rðróròÚfiler^r_rôÚcontextsrörér÷Úreporterr-r-r.rùms1
zCoverage.reportc	CsHtdƒtdƒt|||||dt|ƒ}|j||dWdQRXdS)aDAnnotate a list of modules.

        .. note::

            This method has been obsoleted by more modern reporting tools,
            including the :meth:`html_report` method.  It will be removed in a
            future version.

        Each module in `morfs` is annotated.  The source is written to a new
        file, named with a ",cover" suffix, with each line prefixed with a
        marker to indicate the coverage of the line.  Covered lines have ">",
        excluded lines have "-", and missing lines have "!".

        See :meth:`report` for other arguments.

        z9The annotate command will be removed in a future version.z7Get in touch if you still use it: ned@nedbatchelder.com)ròr@rArõ)Ú	directoryN)r–r/rrù)r]rðrýròr^r_rûrür-r-r.Úannotate¨szCoverage.annotatec
CsBt|||||||||	|
||dt|ƒ}
|
 |¡}|SQRXdS)aEGenerate an HTML report.

        The HTML is written to `directory`.  The file "index.html" is the
        overview starting point, with links to more detailed pages for
        individual modules.

        `extra_css` is a path to a file of other CSS to apply on the page.
        It will be copied into the HTML directory.

        `title` is a text string (not HTML) to use as the title of the HTML
        report.

        See :meth:`report` for other arguments.

        Returns a float, the total percentage covered.

        .. note::

            The HTML report files are generated incrementally based on the
            source files and coverage results. If you modify the report files,
            the changes will not be considered.  You should be careful about
            changing the files in the report folder.

        )ròr@rAZhtml_dirÚ	extra_cssZ
html_titleZhtml_skip_coveredÚ
show_contextsrõZhtml_skip_emptyréN)r/rrù)r]rðrýròr^r_rÿÚtitlerôrrûrörérüÚretr-r-r.Úhtml_reportÆs
zCoverage.html_reportc	Cs:t|||||||dt|jjt|ƒ||jƒSQRXdS)abGenerate an XML report of coverage results.

        The report is compatible with Cobertura reports.

        Each module in `morfs` is included in the report.  `outfile` is the
        path to write the file to, "-" will write to stdout.

        See :meth:`report` for other arguments.

        Returns a float, the total percentage covered.

        )ròr@rAÚ
xml_outputrõröN)r/r$r)rr'r—)r]rðrøròr^r_rûrör-r-r.Ú
xml_reportîszCoverage.xml_reportc		
Cs<t||||||||dt|jjt|ƒ||jƒSQRXdS)aGGenerate a JSON report of coverage results.

        Each module in `morfs` is included in the report.  `outfile` is the
        path to write the file to, "-" will write to stdout.

        See :meth:`report` for other arguments.

        Returns a float, the total percentage covered.

        .. versionadded:: 5.0

        )ròr@rAÚjson_outputrõZjson_pretty_printZjson_show_contextsN)r/r$r)rrr—)	r]rðrøròr^r_rûZpretty_printrr-r-r.Újson_reports

zCoverage.json_reportcCsŠddl}| ¡| ¡dd„}d|jfd|jfd|jrB|j ¡ndfd	trPd
ndfd||jj	ƒfd
||jj
ƒfd||jjƒfd|jj
fd|jjfd|jjfd|jjr²t|jjƒndfd|jdk	rÌ|j ¡ndfdtj dd¡fdt ¡fdt ¡fdtjfdt ¡fdt ¡fdt ¡fdt ¡fdtjfdt d d!„tj! "¡Dƒƒfd"d# #t$td$dgƒ¡fg}|j%rx| &|j% '¡¡| &t( '¡¡|S)%zAReturn a list of (key, value) pairs showing internal information.rNcSs4g}x*|D]"}|j}|js"|d7}| |¡q
W|S)z7Make an entry for the sys_info from a list of plug-ins.z (disabled))r}r±r)reÚentriesrjÚentryr-r-r.Úplugin_info$s
z&Coverage.sys_info.<locals>.plugin_infoZcoverage_versionZcoverage_moduleZtracerz-none-rÚ	availableÚunavailablezplugins.file_tracerszplugins.configurerszplugins.context_switchersZconfigs_attemptedZconfigs_readr6Zconfig_contentsr8rëÚ
ÚÚplatformÚimplementationÚ
executableZdef_encodingZfs_encodingrŠÚcwdržÚenvironmentc3s>|]6\‰}t‡fdd„dDƒƒs(ˆdkrˆ›d|›VqdS)c3s|]}|ˆkVqdS)Nr-)rsr”)rtr-r.r¦Lsz.Coverage.sys_info.<locals>.<genexpr>.<genexpr>)ZCOVZPY)ÚHOMEÚTEMPÚTMPz = N)Úany)rsrur-)rtr.r¦Isz$Coverage.sys_info.<locals>.<genexpr>Zcommand_lineú Úargv))ÚcoveragerkrpÚ__version__Ú__file__rQr°rrRr­rfr©r)Zattempted_config_filesZconfig_files_readr6Z_config_contentsÚreprrPZ
data_filenamerwÚversionÚreplacerÚpython_implementationrÚgetdefaultencodingÚgetfilesystemencodingr‘r’ÚgetcwdržrÚenvironr{r¯rÄrSr¨r|r	)r]Zcovmodr
rr-r-r.r|sF








zCoverage.sys_info)NF)r¾)r¾)r¾)NFF)N)NNNNNNNNNNN)NNNNNN)NNNNNNNNNNNN)NNNNNNN)NNNNNNNN).Ú__name__Ú
__module__Ú__qualname__Ú__doc__r3Úclassmethodr5rErarkrprnr…rˆr[r—r˜ršr£rµr r·r¹r´r¼r½rÃr¾rÁrÈrÉr»rØrÊrÙrärßrårèrñrùrþrrrr|r-r-r-r.r1Asn
(
Q 		




0

9

%

r1ZCOVERAGE_DEBUG_CALLS)Údecorate_methodsÚ
show_callsT)Z	show_argsrÊ)ZbutnotcCsVtj d¡}|sdSttdƒr"dSt|d}|t_d|_d|_d|_	d|_
| ¡|S)aµCall this at Python start-up to perhaps measure coverage.

    If the environment variable COVERAGE_PROCESS_START is defined, coverage
    measurement is started.  The value of the variable is the config file
    to use.

    There are two ways to configure your Python installation to invoke this
    function when Python starts:

    #. Create or append to sitecustomize.py to add these lines::

        import coverage
        coverage.process_startup()

    #. Create a .pth file in your Python installation containing::

        import coverage; coverage.process_startup()

    Returns the :class:`Coverage` instance that was started, or None if it was
    not started by this call.

    ZCOVERAGE_PROCESS_STARTNr)r6FT)r‘r$rìÚhasattrÚprocess_startupr1rrJrKrLrHr·)Zcpsr+r-r-r.r-cs

r-cCsttddƒ}|dk	rd|_dS)z7Stop any subprocess auto-measurement from writing data.rNF)rÄr-rH)Zauto_created_coverager-r-r.r\˜sr\)Sr(r²rÚÚ
contextlibr‘Úos.pathrrwrir“rrZcoverage.annotaterZcoverage.collectorrrZcoverage.configrZcoverage.contextrrZ
coverage.datar	r
Zcoverage.debugrrr
Zcoverage.dispositionrZcoverage.exceptionsrrrrZcoverage.filesrrrrZ
coverage.htmlrZcoverage.inoroutrZcoverage.jsonreportrZ
coverage.miscrrrrrrr Zcoverage.pluginr!Zcoverage.plugin_supportr"Zcoverage.pythonr#Zcoverage.reportr$Zcoverage.resultsr%Zcoverage.summaryr&Zcoverage.xmlreportr'Zcoverage.multiprocr(ÚImportErrorÚcontextmanagerr/rEr1rhr$rìr*r+r-r\r-r-r-r.Ú<module>sh
$5

Products

About

Resources

Contact Gemfury