⚝
One Hat Cyber Team
⚝
Your IP:
216.73.216.62
Server IP:
57.129.66.90
Server:
Linux vps-7f548908 5.15.0-164-generic #174-Ubuntu SMP Fri Nov 14 20:25:16 UTC 2025 x86_64
Server Software:
LiteSpeed
PHP Version:
8.2.27
Buat File
|
Buat Folder
Eksekusi
Dir :
~
/
snap
/
core20
/
2686
/
usr
/
lib
/
python3.8
/
__pycache__
/
Edit File: doctest.cpython-38.pyc
U >h_ ! @ st d Z dZdddddddd d d d d ddddddddddddddd d d d d d!d"g!Zd#d$lZd#d$lZd#d$lZd#d$lZd#d$lZd#d$lZd#d$l Z d#d$l Z d#d$l Z d#d$l Z d#d%l mZ d#d&lmZ ed'd(Zi Zd)d ZedZedZedZedZedZedZeeB eB eB eB eB Zed Zed Z ed Z ed Z edZ ee B e B e B e B Z d*Z!d+Z"d,d- Z#dsd/d0Z$d1d2 Z%d3d4 Z&dtd6d7Z'd8d9 Z(G d:d; d;eZ)d<d= Z*d>d? Z+d@dA Z,G dBdC dCej-Z.dDdE Z/G dFd dZ0G dGd dZ1G dHd dZ2G dId dZ3G dJd dZ4G dKd dZ5G dLd de6Z7G dMd de6Z8G dNd de4Z9d$a:dudQdZ;dOd$d$d$d$dOd#d$dPe2 d$f dRdZ<dvdTdZ=d#a>dUd Z?G dVdW dWe j@ZAG dXdY dYeAZBG dZd[ d[e jCZDdwd\d ZEG d]d^ d^eAZFdOd$d$e2 d$fd_d`ZGdad ZHdbd ZIdcd ZJdxddd!ZKdydedfZLdzdgd"ZMG dhdi diZNeNdjdkdldmdndoZOdpdq ZPeQdrkrpe ReP d$S ){a Module doctest -- a framework for running examples in docstrings. In simplest use, end each module M to be tested with: def _test(): import doctest doctest.testmod() if __name__ == "__main__": _test() Then running the module as a script will cause the examples in the docstrings to get executed and verified: python M.py This won't display anything unless an example fails, in which case the failing example(s) and the cause(s) of the failure(s) are printed to stdout (why not stderr? because stderr is a lame hack <0.2 wink>), and the final line of output is "Test failed.". Run it with the -v switch instead: python M.py -v and a detailed report of all examples tried is printed to stdout, along with assorted summaries at the end. You can force verbose mode by passing "verbose=True" to testmod, or prohibit it by passing "verbose=False". In either of those cases, sys.argv is not examined by testmod. There are a variety of other ways to run doctests, including integration with the unittest framework, and support for running non-Python text files containing doctests. There are also many ways to override parts of doctest's default behaviors. See the Library Reference Manual for details. zreStructuredText enregister_optionflagDONT_ACCEPT_TRUE_FOR_1DONT_ACCEPT_BLANKLINENORMALIZE_WHITESPACEELLIPSISSKIPIGNORE_EXCEPTION_DETAILCOMPARISON_FLAGS REPORT_UDIFF REPORT_CDIFF REPORT_NDIFFREPORT_ONLY_FIRST_FAILUREREPORTING_FLAGS FAIL_FASTExampleDocTest DocTestParser DocTestFinder DocTestRunner OutputCheckerDocTestFailureUnexpectedException DebugRunnertestmodtestfilerun_docstring_examples DocTestSuite DocFileSuiteset_unittest_reportflagsscript_from_examples testsource debug_srcdebug N)StringIO) namedtuple TestResultszfailed attemptedc C s t | dtt > S )N )OPTIONFLAGS_BY_NAME setdefaultlenname r, /usr/lib/python3.8/doctest.pyr s z <BLANKLINE>z...c C s8 d}t jD ](}| |d}|tt |kr ||jO }q |S )z Return the compiler-flags associated with the future features that have been imported into the given namespace (globs). r" N) __future__Zall_feature_namesgetgetattrZ compiler_flag)globsflagsZfnameZfeaturer, r, r- _extract_future_flags s r3 c C sV t | r| S t| tr,t| t t dgS | dkrJtjt |j d S t ddS )a Return the module specified by `module`. In particular: - If `module` is a module, then return module. - If `module` is a string, then import and return the module with that name. - If `module` is None, then return the calling module. The calling module is assumed to be the module of the stack frame at the given depth in the call stack. *N__name__z"Expected a module, string, or None) inspectismodule isinstancestr __import__globalslocalssysmodules _getframe f_globals TypeError)moduleZdepthr, r, r- _normalize_module s rD c C s dD ]}| |d} q| S )N)z )replace)datanewliner, r, r- _newline_convert s rJ c C s |rVt |d}t|| } t|dd d k rVt|jdrV|j| }||}t|| fS t| |d}| | fW 5 Q R S Q R X d S )N __loader__get_data)encoding) rD _module_relative_pathr0 hasattrrL rM decoderJ openread)filenamepackagemodule_relativerN Z file_contentsfr, r, r- _load_testfile s rX c C s t d|d | S )z~ Add the given number of space characters to the beginning of every non-blank line in `s`, and return the result. z (?m)^(?!$) )resub)sindentr, r, r- _indent s r_ c C s* t }| \}}}tj||||d | S )zz Return a string containing a traceback message for the given exc_info tuple (as returned by sys.exc_info()). )file)r# tracebackprint_exceptiongetvalue)exc_infoZexcoutexc_typeZexc_valZexc_tbr, r, r- _exception_traceback s rf c @ s e Zd Zdd ZdddZdS ) _SpoofOutc C s$ t | }|r |ds |d7 }|S NrF )r# rc endswith)selfresultr, r, r- rc s z_SpoofOut.getvalueNc C s | | t| d S N)seekr# truncate)rj sizer, r, r- rn s z_SpoofOut.truncate)N)r6 __module__ __qualname__rc rn r, r, r, r- rg s rg c C s t | kr| |kS | t }t|dks*tdt| }}|d }|rb||r^t|}|d= ndS |d }|r||r|t|8 }|d= ndS ||krdS |D ],}||||}|dk r dS |t|7 }qdS )z_ Essentially the only subtle case: >>> _ellipsis_match('aa...aa', 'aaa') False r4 r" FT)ELLIPSIS_MARKERsplitr) AssertionError startswithri find)wantgotZwsstartposendposwr, r, r- _ellipsis_match s2 r} c C s | } | rd| S dS dS )z)Return a commented form of the given linez# #N)rstrip)liner, r, r- _comment_line? s r c C sh dt | }}| d}|dkr$|}| dd|}|dkr>|}| dd|}|dkr\|d }| || S )Nr" rF :.r& )r) rw rfind)msgstartendir, r, r- _strip_exception_detailsG s r c @ s2 e Zd ZdZdd Zd ddZdd Zd d ZdS ) _OutputRedirectingPdbz A specialized version of the python debugger that redirects stdout to a given stream when interacting with the user. Stdout is *not* redirected when traced code is executed. c C s( || _ d| _tjj| |dd d| _d S )NFT)stdoutnosigintr& )_OutputRedirectingPdb__out$_OutputRedirectingPdb__debugger_usedpdbPdb__init__Z use_rawinput)rj outr, r, r- r g s z _OutputRedirectingPdb.__init__Nc C s* d| _ |d krt j}tj| | d S )NT)r r> r@ f_backr r set_trace)rj framer, r, r- r o s z _OutputRedirectingPdb.set_tracec C s | j rtj| d S rl )r r r set_continuerj r, r, r- r u s z"_OutputRedirectingPdb.set_continuec G s2 t j}| jt _ztjj| f| W S |t _X d S rl )r> r r r r trace_dispatch)rj args save_stdoutr, r, r- r { s z$_OutputRedirectingPdb.trace_dispatch)N)r6 rp rq __doc__r r r r r, r, r, r- r a s r c C s t | std| |dr(tdtjj|d }t | drXtj| j d }n| j dkrt t jdkrt jd dkrtjt jd d }qtj}nFt | dr| jD ]&}tj||}tj|r| S qtd | j tj||S ) NzExpected a module: %r/z1Module-relative files may not have absolute paths__file__r" __main__ __path__zBCan't resolve paths relative to the module %r (it has no __file__))r7 r8 rB rv ValueErrorospathjoinrt rP r r6 r) r> argvcurdirr exists)rC Z test_pathZbasedirZ directoryfullpathr, r, r- rO s( rO c @ s* e Zd ZdZd ddZdd Zdd ZdS ) r an A single doctest example, consisting of source code and expected output. `Example` defines the following attributes: - source: A single Python statement, always ending with a newline. The constructor adds a newline if needed. - want: The expected output from running the source code (either from stdout, or a traceback in case of exception). `want` ends with a newline unless it's empty, in which case it's an empty string. The constructor adds a newline if needed. - exc_msg: The exception message generated by the example, if the example is expected to generate an exception; or `None` if it is not expected to generate an exception. This exception message is compared against the return value of `traceback.format_exception_only()`. `exc_msg` ends with a newline unless it's `None`. The constructor adds a newline if needed. - lineno: The line number within the DocTest string containing this Example where the Example begins. This line number is zero-based, with respect to the beginning of the DocTest. - indent: The example's indentation in the DocTest string. I.e., the number of space characters that precede the example's first prompt. - options: A dictionary mapping from option flags to True or False, which is used to override default options for this example. Any option flags not contained in this dictionary are left at their default value (as specified by the DocTestRunner's optionflags). By default, no options are set. Nr" c C sv | ds|d7 }|r(| ds(|d7 }|d k rB| dsB|d7 }|| _|| _|| _|| _|d krfi }|| _|| _d S rh )ri sourcerx linenor^ optionsexc_msg)rj r rx r r r^ r r, r, r- r s zExample.__init__c C s\ t | t |k rtS | j|jkoZ| j|jkoZ| j|jkoZ| j|jkoZ| j|jkoZ| j|jkS rl )typeNotImplementedr rx r r^ r r rj otherr, r, r- __eq__ s zExample.__eq__c C s t | j| j| j| j| jfS rl )hashr rx r r^ r r r, r, r- __hash__ s zExample.__hash__)Nr" r" N)r6 rp rq r r r r r, r, r, r- r s " c @ s8 e Zd ZdZdd Zdd Zdd Zdd Zd d Zd S ) r ae A collection of doctest examples that should be run in a single namespace. Each `DocTest` defines the following attributes: - examples: the list of examples. - globs: The namespace (aka globals) that the examples should be run in. - name: A name identifying the DocTest (typically, the name of the object whose docstring this DocTest was extracted from). - filename: The name of the file that this DocTest was extracted from, or `None` if the filename is unknown. - lineno: The line number within filename where this DocTest begins, or `None` if the line number is unavailable. This line number is zero-based, with respect to the beginning of the file. - docstring: The string that the examples were extracted from, or `None` if the string is unavailable. c C s> t |trtd|| _|| _| | _|| _|| _|| _ dS )z Create a new DocTest containing the given examples. The DocTest's globals are initialized with a copy of `globs`. z8DocTest no longer accepts str; use DocTestParser insteadN) r9 r: ru examples docstringcopyr1 r+ rT r )rj r r1 r+ rT r r r, r, r- r s zDocTest.__init__c C sR t | jdkrd}n"t | jdkr(d}ndt | j }d| jj| j| j| j|f S )Nr" z no examplesr& z 1 examplez %d examplesz<%s %s from %s:%s (%s)>)r) r __class__r6 r+ rT r )rj r r, r, r- __repr__ s zDocTest.__repr__c C s\ t | t |k rtS | j|jkoZ| j|jkoZ| j|jkoZ| j|jkoZ| j|jkoZ| j|jkS rl )r r r r r1 r+ rT r r r, r, r- r ) s zDocTest.__eq__c C s t | j| j| j| jfS rl )r r r+ rT r r r, r, r- r 4 s zDocTest.__hash__c C s: t |tstS | j| j| jt| f|j|j|jt|fk S rl )r9 r r r+ rT r idr r, r, r- __lt__8 s zDocTest.__lt__N) r6 rp rq r r r r r r r, r, r, r- r s c @ s e Zd ZdZedejejB ZedejejB ej B Z edj Z dddZ dd Zdd d Zd d ZedejZdd ZedejZdd Zdd Zdd ZdS )r zD A class used to parse strings containing doctest examples. a # Source consists of a PS1 line followed by zero or more PS2 lines. (?P<source> (?:^(?P<indent> [ ]*) >>> .*) # PS1 line (?:\n [ ]* \.\.\. .*)*) # PS2 lines \n? # Want consists of any non-blank lines that do not start with PS1. (?P<want> (?:(?![ ]*$) # Not a blank line (?![ ]*>>>) # Not a line starting with PS1 .+$\n? # But any other line )*) a # Grab the traceback header. Different versions of Python have # said different things on the first traceback line. ^(?P<hdr> Traceback\ \( (?: most\ recent\ call\ last | innermost\ last ) \) : ) \s* $ # toss trailing whitespace on the header. (?P<stack> .*?) # don't blink: absorb stuff until... ^ (?P<msg> \w+ .*) # a line *starts* with alphanum. z ^[ ]*(#.*)?$<string>c s | }| | dkr8d fdd|dD }g }d\}}| j|D ]}|||| ||d|| 7 }| |||\}}} } | |s|t || | | t | d |d ||d| | 7 }| }qP|||d |S ) a= Divide the given string into examples and intervening text, and return them as a list of alternating Examples and strings. Line numbers for the Examples are 0-based. The optional argument `name` is a name identifying this string, and is only used for error messages. r" rF c s g | ]}| d qS rl r, .0lZ min_indentr, r- <listcomp> s z'DocTestParser.parse.<locals>.<listcomp>r" r" r^ )r r^ r N) expandtabs _min_indentr rt _EXAMPLE_REfinditerappendr count_parse_example_IS_BLANK_OR_COMMENTr r) groupr ) rj stringr+ outputZcharnor mr r rx r r, r r- parses s* zDocTestParser.parsec C s t | |||||||S )a" Extract all doctest examples from the given string, and collect them into a `DocTest` object. `globs`, `name`, `filename`, and `lineno` are attributes for the new `DocTest` object. See the documentation for `DocTest` for more information. )r get_examples)rj r r1 r+ rT r r, r, r- get_doctest s zDocTestParser.get_doctestc C s dd | ||D S )a Extract all doctest examples from the given string, and return them as a list of `Example` objects. Line numbers are 0-based, because it's most common in doctests that nothing interesting appears on the same line as opening triple-quote, and so the first interesting line is called "line 1" then. The optional argument `name` is a name identifying this string, and is only used for error messages. c S s g | ]}t |tr|qS r, )r9 r )r xr, r, r- r s z.DocTestParser.get_examples.<locals>.<listcomp>)r )rj r r+ r, r, r- r s zDocTestParser.get_examplesc s t |d |dd}| | || | |dd d d || d fdd |D }|d }|d}t |dkrtd |d r|d = | |d ||t | d fd d |D }| j|}|r|d}nd}| |||} || ||fS )a Given a regular expression match from `_EXAMPLE_RE` (`m`), return a pair `(source, want)`, where `source` is the matched example's source code (with prompts and indentation stripped); and `want` is the example's expected output (with indentation stripped). `name` is the string's name, and `lineno` is the line number where the example starts; both are used for error messages. r^ r rF r& NrZ r c s g | ]}| d d qS )rY Nr, )r Zslr^ r, r- r s z0DocTestParser._parse_example.<locals>.<listcomp>rx z *$rr c s g | ]}| d qS rl r, )r Zwlr r, r- r s r ) r) r rt _check_prompt_blank _check_prefixr r[ match _EXCEPTION_RE _find_options) rj r r+ r source_linesr rx want_linesr r r, r r- r s& z DocTestParser._parse_examplez#\s*doctest:\s*([^\n\'"]*)$c C s i }| j |D ]v}|ddd }|D ]V}|d dksN|dd tkrdtd|d ||f t|dd }|d dk||< q.q|r| |rtd |||f |S ) a Return a dictionary containing option overrides extracted from option directives in the given source string. `name` is the string's name, and `lineno` is the line number where the example starts; both are used for error messages. r& ,rZ r" z+-Nz7line %r of the doctest for %s has an invalid option: %r+zSline %r of the doctest for %s has an option directive on a line with no example: %r)_OPTION_DIRECTIVE_REr r rG rt r' r r ) rj r r+ r r r Zoption_stringsoptionflagr, r, r- r s" zDocTestParser._find_optionsz ^([ ]*)(?=\S)c C s2 dd | j |D }t|dkr*t|S dS dS )z;Return the minimum indentation of any non-blank line in `s`c S s g | ] }t |qS r, )r) )r r^ r, r, r- r s z-DocTestParser._min_indent.<locals>.<listcomp>r" N) _INDENT_REfindallr) min)rj r] indentsr, r, r- r s zDocTestParser._min_indentc C s^ t |D ]P\}}t||d kr||d dkrtd|| d ||||d |f qdS )a Given the lines of a source string (including prompts and leading indentation), check to make sure that every prompt is followed by a space character. If any line is not followed by a space character, then raise ValueError. rY rK rZ z8line %r of the docstring for %s lacks blank after %s: %rr& N) enumerater) r )rj linesr^ r+ r r r r, r, r- r s z!DocTestParser._check_prompt_blankc C s> t |D ]0\}}|r||std|| d ||f qdS )z Check that every line in the given list starts with the given prefix; if any line does not, then raise a ValueError. zGline %r of the docstring for %s has inconsistent leading whitespace: %rr& N)r rv r )rj r prefixr+ r r r r, r, r- r s zDocTestParser._check_prefixN)r )r )r6 rp rq r r[ compile MULTILINEVERBOSEr DOTALLr r r r r r r r r r r r r r, r, r, r- r C s( ' 3 c @ sN e Zd ZdZde ddfddZdddZd d Zd d Zd d Z dd Z dS )r a< A class used to extract the DocTests that are relevant to a given object, from its docstring and the docstrings of its contained objects. Doctests can currently be extracted from the following object types: modules, functions, classes, methods, staticmethods, classmethods, and properties. FTc C s || _ || _|| _|| _dS )at Create a new doctest finder. The optional argument `parser` specifies a class or function that should be used to create new DocTest objects (or objects that implement the same interface as DocTest). The signature for this factory function should match the signature of the DocTest constructor. If the optional argument `recurse` is false, then `find` will only examine the given object, and not any contained objects. If the optional argument `exclude_empty` is false, then `find` will include tests for objects with empty docstrings. N)_parser_verbose_recurse_exclude_empty)rj verboseparserrecurse exclude_emptyr, r, r- r 7 s zDocTestFinder.__init__Nc C sN |dkr.t |dd}|dkr.tdt|f |dkr<d}n|dkrNt|}zt|}W n tk rt d}Y ndX |st|}|d |dd dksd}|dkrd}n*|dk rt ||j }n t |}|sd}|dkr|dkri }n |j }n| }|dk r| | d|kr(d|d< g }| ||||||i | |S ) aj Return a list of the DocTests that are defined by the given object's docstring, or by any of its contained objects' docstrings. The optional parameter `module` is the module that contains the given object. If the module is not specified or is None, then the test finder will attempt to automatically determine the correct module. The object's module is used: - As a default namespace, if `globs` is not specified. - To prevent the DocTestFinder from extracting DocTests from objects that are imported from other modules. - To find the name of the file containing the object. - To help find the line number of the object within its file. Contained objects whose module does not match `module` are ignored. If `module` is False, no attempt to find the module will be made. This is obscure, of use mostly in tests: if `module` is False, or is None but cannot be found automatically, then all objects are considered to belong to the (non-existent) module, so all contained objects will (recursively) be searched for doctests. The globals for each DocTest is formed by combining `globs` and `extraglobs` (bindings in `extraglobs` override bindings in `globs`). A new copy of the globals dictionary is created for each DocTest. If `globs` is not specified, then it defaults to the module's `__dict__`, if specified, or {} otherwise. If `extraglobs` is not specified, then it defaults to {}. Nr6 zJDocTestFinder.find: name must be given when obj.__name__ doesn't exist: %rFr" z<]>r )r0 r r r7 getmoduleZ getsourcefilerB Zgetfile linecachegetlines__dict__r update_findsort) rj objr+ rC r1 extraglobsr` r testsr, r, r- rw M sL $ zDocTestFinder.findc C s |dkr dS t |dk r(|t |kS t |r>|j|jkS t |r|t|dr\|jj}nt|drn|j}ndS |j |kS t |r|j |jkS t|dr|j |jkS t |t rdS t ddS )zY Return true if the given object is defined in the given module. NT __objclass__rp z"object must be a class or function)r7 r isfunctionr __globals__ZismethoddescriptorrP r rp r6 isclassr9 propertyr )rj rC objectZobj_modr, r, r- _from_module s( zDocTestFinder._from_modulec C s | j rtd| t||kr"dS d|t|< | |||||}|dk rR|| t|r| jr|j D ]P\} } d|| f } t t | st | rl| || rl| || | |||| qlt|rn| jrnt|di D ]\} } t| tstdt| f t | sJt | sJt| sJt| tsJtdt| f d|| f } | || | |||| qt |r| jr|j D ]\} } t| trt|| } t| trt|| j} t | st | st| tr| || rd|| f } | || | |||| qdS ) zm Find tests for the given object and any contained objects, and add them to `tests`. zFinding tests in %sNr& z%s.%s__test__z5DocTestFinder.find: __test__ keys must be strings: %rz`DocTestFinder.find: __test__ values must be strings, functions, methods, classes, or modules: %rz%s.__test__.%s)r printr _get_testr r7 r8 r r itemsZ isroutineZunwrapr r r r0 r9 r: r r staticmethod classmethod__func__r ) rj r r r+ rC r r1 seentestZvalnamevalr, r, r- r sn zDocTestFinder._findc C s t |tr|}nJz,|jdkr"d}n|j}t |ts:t|}W n ttfk rX d}Y nX | ||}| jrt|stdS |dkrd}n.t|ddp|j}|dd dkr|dd }| j |||||S )zs Return a DocTest for the given object, if it defines a docstring; otherwise, return None. Nr r .pycrr ) r9 r: r rB AttributeError _find_linenor r0 r6 r r ) rj r r+ rC r1 r r r rT r, r, r- r s, zDocTestFinder._get_testc C s d}t |rd}t |rb|dkr(dS tdt|dd }t|D ]\}}||rF|} qbqFt |rr|j }t |r|j }t |r|j }t |r|j}t |rt|ddd }|dk r |dkr|d S td}t|t|D ]}||| r| S qdS ) z Return a line number of the given object's docstring. Note: this method assumes that the object has a docstring. Nr" z^\s*class\s*%s\br6 -co_firstlinenor& z(^|.*:)\s*\w*("|\'))r7 r8 r r[ r r0 r r Zismethodr r __code__Z istracebacktb_frameZisframef_codeZiscoderanger) )rj r r r Zpatr r r, r, r- r 4 s> zDocTestFinder._find_lineno)NNNN) r6 rp rq r r r rw r r r r r, r, r, r- r . s f ?&c @ s e Zd ZdZdZd ddZdd Zd d Zd d Zd d Z dd Z dd Z dd Z e dZd ddZd!ddZd"dd Zd d ZdS )#r a3 A class used to run DocTest test cases, and accumulate statistics. The `run` method is used to process a single DocTest case. It returns a tuple `(f, t)`, where `t` is the number of test cases tried, and `f` is the number of test cases that failed. >>> tests = DocTestFinder().find(_TestClass) >>> runner = DocTestRunner(verbose=False) >>> tests.sort(key = lambda test: test.name) >>> for test in tests: ... print(test.name, '->', runner.run(test)) _TestClass -> TestResults(failed=0, attempted=2) _TestClass.__init__ -> TestResults(failed=0, attempted=2) _TestClass.get -> TestResults(failed=0, attempted=2) _TestClass.square -> TestResults(failed=0, attempted=1) The `summarize` method prints a summary of all the test cases that have been run by the runner, and returns an aggregated `(f, t)` tuple: >>> runner.summarize(verbose=1) 4 items passed all tests: 2 tests in _TestClass 2 tests in _TestClass.__init__ 2 tests in _TestClass.get 1 tests in _TestClass.square 7 tests in 4 items. 7 passed and 0 failed. Test passed. TestResults(failed=0, attempted=7) The aggregated number of tried examples and failed examples is also available via the `tries` and `failures` attributes: >>> runner.tries 7 >>> runner.failures 0 The comparison between expected outputs and actual outputs is done by an `OutputChecker`. This comparison may be customized with a number of option flags; see the documentation for `testmod` for more information. If the option flags are insufficient, then the comparison may also be customized by passing a subclass of `OutputChecker` to the constructor. The test runner's display output can be controlled in two ways. First, an output function (`out) can be passed to `TestRunner.run`; this function will be called with strings that should be displayed. It defaults to `sys.stdout.write`. If capturing the output is not sufficient, then the display output can be also customized by subclassing DocTestRunner, and overriding the methods `report_start`, `report_success`, `report_unexpected_exception`, and `report_failure`. zF**********************************************************************Nr" c C sN |pt | _|dkr dtjk}|| _|| _|| _d| _d| _i | _ t | _ dS )ac Create a new test runner. Optional keyword arg `checker` is the `OutputChecker` that should be used to compare the expected outputs and actual outputs of doctest examples. Optional keyword arg 'verbose' prints lots of stuff if true, only failures if false; by default, it's true iff '-v' is in sys.argv. Optional argument `optionflags` can be used to control how the test runner compares expected output to actual output, and how it displays failures. See the documentation for `testmod` for more information. N-vr" ) r _checkerr> r r optionflagsoriginal_optionflagstriesfailures_name2ftrg _fakeout)rj checkerr r r, r, r- r s zDocTestRunner.__init__c C sH | j rD|jr.|dt|j d t|j n|dt|j d dS )z Report that the test runner is about to process the given example. (Only displays a message if verbose=True) zTrying: z Expecting: zExpecting nothing N)r rx r_ r )rj r r exampler, r, r- report_start s zDocTestRunner.report_startc C s | j r|d dS )zt Report that the given example ran successfully. (Only displays a message if verbose=True) zok N)r rj r r r! ry r, r, r- report_success s z DocTestRunner.report_successc C s& || ||| j||| j dS )z7 Report that the given example failed. N)_failure_headerr output_differencer r# r, r, r- report_failure s z DocTestRunner.report_failurec C s$ || ||d tt| dS )zO Report that the given example raised an unexpected exception. zException raised: N)r% r_ rf rj r r r! rd r, r, r- report_unexpected_exception s z)DocTestRunner.report_unexpected_exceptionc C s | j g}|jrR|jd k r4|jd k r4|j|j d }nd}|d|j||jf n|d|jd |jf |d |j}|t| d|S )Nr& ?zFile "%s", line %s, in %szLine %s, in %szFailed example:rF )DIVIDERrT r r r+ r r_ r )rj r r! r r r r, r, r- r% s z DocTestRunner._failure_headerc C s d }}| j }td\}}} | jj} t|jD ]H\} } | j t@ oH|dk} || _ | jr| j D ],\}}|r|| j |O _ q`| j | M _ q`| j t @ rq.|d7 }| s| ||| d|j | f }z,t t | j|d|d|j | j d}W n4 tk r Y n t }| j Y nX | j }| jd |}|dkr`| | j|| j r|}n|tj|dd d }| s|t|7 }| j dkr| }nB| | j || j r|}n*| j t @ r| t | j t || j r|}||kr| sd| ||| | nf||kr(| s | ||| | |d7 }n<|| krR| sH| !||| | |d7 }nd sdt"d |f|r.| j t#@ r. qzq.|| _ | $||| t%||S ) a Run the examples in `test`. Write the outcome of each example with one of the `DocTestRunner.report_*` methods, using the writer function `out`. `compileflags` is the set of compiler flags that should be used to execute examples. Return a tuple `(f, t)`, where `t` is the number of examples tried, and `f` is the number of examples that failed. The examples are run in the namespace `test.globs`. r" rK r& z<doctest %s[%d]>ZsingleNr4 rr Fzunknown outcome)&r r r check_outputr r r r r r r" r+ execr r r1 debuggerr KeyboardInterruptr> rd r rc rn rx ra format_exception_onlyrf r r r r$ r' r) ru r _DocTestRunner__record_outcomer% )rj r compileflagsr r r r SUCCESSFAILUREZBOOMZcheck examplenumr! quietZ optionflagr rT Z exceptionry Zoutcomer r, r, r- Z__run s zDocTestRunner.__runc C sL | j |jd\}}|| || f| j |j< | j|7 _| j|7 _dS )z{ Record the fact that the given DocTest (`test`) generated `f` failures out of `t` tried examples. r N)r r/ r+ r r )rj r rW tf2t2r, r, r- Z__record_outcome| s z DocTestRunner.__record_outcomez.<doctest (?P<name>.+)\[(?P<examplenum>\d+)\]>$c C sV | j |}|rF|d| jjkrF| jjt|d }|jjddS | ||S d S )Nr+ r5 Tkeepends) %_DocTestRunner__LINECACHE_FILENAME_REr r r r+ r intr splitlinessave_linecache_getlines)rj rT module_globalsr r! r, r, r- Z __patched_linecache_getlines s z*DocTestRunner.__patched_linecache_getlinesTc s || _ |dkrt|j}tj|dkrVj dks@ dkrHj}n fdd}| jt_t }t j }t | _ | j | j j t _ tj| _| jt_tj}tjt_z| |||W S t_|t _ t| | jt_|t_| r|j ddl}d|_X dS )aJ Run the examples in `test`, and display the results using the writer function `out`. The examples are run in the namespace `test.globs`. If `clear_globs` is true (the default), then this namespace will be cleared after the test runs, to help with garbage collection. If you would like to examine the namespace after the test completes, then use `clear_globs=False`. `compileflags` gives the set of flags that should be used by the Python compiler when running the examples. If not specified, then it will default to the set of future-import flags that apply to `globs`. The output of each example is checked using `DocTestRunner.check_output`, and the results are formatted by the `DocTestRunner.report_*` methods. Nutf-8c s t | d } | d S )Nbackslashreplace)r: encodewrite)r] rN r r, r- r s z DocTestRunner.run.<locals>.outr" )r r3 r1 r> r rN lowerrD r gettracer r r r. resetr r r? *_DocTestRunner__patched_linecache_getlines displayhook__displayhook__settraceclearbuiltins__DocTestRunner__run) rj r r2 r clear_globsZ save_traceZsave_set_traceZsave_displayhookrN r, rE r- run s< zDocTestRunner.runc C s |dkr| j }g }g }g }d }}| j D ]b}|\}\} } | | ksHt|| 7 }|| 7 }| dkrl|| q,| dkr||| f q,|| q,|r|rtt|d | |D ]} td| q|rtt|d | |D ]\} } td| | f q|rFt| j tt|d | |D ] \} \} } td| | | f q$|rrt|d t| jd t|| d |d |rtd |d n|rtd t ||S )a Print a summary of all the test cases that have been run by this DocTestRunner, and return a tuple `(f, t)`, where `f` is the total number of failed examples, and `t` is the total number of tried examples. The optional `verbose` argument controls how detailed the summary is. If the verbosity is not specified, then the DocTestRunner's verbosity is used. Nr" zitems had no tests:z zitems passed all tests:z %3d tests in %szitems had failures:z %3d of %3d in %sztests inzitems.z passed andzfailed.z***Test Failed***z failures.z Test passed.) r r r ru r r r) r r+ r% ) rj r ZnotestsZpassedZfailedZtotaltZtotalfr r+ rW r7 thingr r, r, r- summarize sR zDocTestRunner.summarizec C sR | j }|j D ]<\}\}}||kr@|| \}}|| }|| }||f||< qd S rl )r r )rj r dr+ rW r7 r8 r9 r, r, r- merge s zDocTestRunner.merge)NNr" )N)NNT)N)r6 rp rq r r+ r r" r$ r' r) r% rP r1 r[ r r< rI rR rT rV r, r, r, r- r h s 9 $ } I 9c @ s0 e Zd ZdZdd Zdd Zdd Zdd Zd S ) r a_ A class used to check the whether the actual output from a doctest example matches the expected output. `OutputChecker` defines two methods: `check_output`, which compares a given pair of outputs, and returns true if they match; and `output_difference`, which returns a string describing the differences between two outputs. c C s t |dddS )z= Convert string to hex-escaped ASCII string. ASCIIrB )r: rC )rj r] r, r, r- _toAscii( s zOutputChecker._toAsciic C s | |}| |}||kr dS |t@ sH||fdkr8dS ||fdkrHdS |t@ stdtt d|}tdd|}||krdS |t@ rd| }d| }||krdS |t @ rt ||rdS dS ) a Return True iff the actual output from an example (`got`) matches the expected output (`want`). These strings are always considered to match if they are identical; but depending on what option flags the test runner is using, several non-exact match types are also possible. See the documentation for `TestRunner` for more information about option flags. T)zTrue z1 )zFalse z0 z (?m)^%s\s*?$r z(?m)^[^\S\n]+$rZ F) rX r r r[ r\ escapeBLANKLINE_MARKERr r rt r r} rj rx ry r r, r, r- r, . s4 zOutputChecker.check_outputc C s< |t tB tB @ sdS |t@ r dS |ddko:|ddkS )NFTrF r4 )r r r r r[ r, r, r- _do_a_fancy_diffm s z OutputChecker._do_a_fancy_diffc C s8 |j }|t@ s tdt|}| |||r|jdd}|jdd}|t@ rptj ||dd}t |dd }d}nf|t @ rtj ||dd}t |dd }d}n8|t @ rtjtjd } t | ||}d }n d std d | td| S |r |r dt|t|f S |r dt| S |r0dt| S dS dS )z Return a string describing the differences between the expected output for a given example (`example`) and the actual output (`got`). `optionflags` is the set of option flags used to compare `want` and `got`. z(?m)^[ ]*(?= )Tr: r4 )nNz#unified diff with -expected +actualz-context diff with expected followed by actual)Zcharjunkz ndiff with -expected +actualr" zBad diff optionzDifferences (%s): r zExpected: %sGot: %szExpected: %sGot nothing zExpected nothing Got: %sz Expected nothing Got nothing )rx r r[ r\ rZ r\ r> r difflibZ unified_difflistr Z context_diffr ZDifferZIS_CHARACTER_JUNKZcompareru r_ r ) rj r! ry r rx r Z got_linesZdiffZkindZenginer, r, r- r& s6 z OutputChecker.output_differenceN)r6 rp rq r rX r, r\ r& r, r, r, r- r s ?c @ s e Zd ZdZdd Zdd ZdS )r zA DocTest example has failed in debugging mode. The exception instance has variables: - test: the DocTest object being run - example: the Example object that failed - got: the actual output c C s || _ || _|| _d S rl )r r! ry )rj r r! ry r, r, r- r s zDocTestFailure.__init__c C s t | jS rl r: r r r, r, r- __str__ s zDocTestFailure.__str__Nr6 rp rq r r ra r, r, r, r- r s c @ s e Zd ZdZdd Zdd ZdS )r zA DocTest example has encountered an unexpected exception The exception instance has variables: - test: the DocTest object being run - example: the Example object that failed - exc_info: the exception info c C s || _ || _|| _d S rl )r r! rd )rj r r! rd r, r, r- r s z UnexpectedException.__init__c C s t | jS rl r` r r, r, r- ra s zUnexpectedException.__str__Nrb r, r, r, r- r s c @ s* e Zd ZdZd ddZdd Zdd ZdS ) r a Run doc tests but raise an exception as soon as there is a failure. If an unexpected exception occurs, an UnexpectedException is raised. It contains the test, the example, and the original exception: >>> runner = DebugRunner(verbose=False) >>> test = DocTestParser().get_doctest('>>> raise KeyError\n42', ... {}, 'foo', 'foo.py', 0) >>> try: ... runner.run(test) ... except UnexpectedException as f: ... failure = f >>> failure.test is test True >>> failure.example.want '42\n' >>> exc_info = failure.exc_info >>> raise exc_info[1] # Already has the traceback Traceback (most recent call last): ... KeyError We wrap the original exception to give the calling application access to the test and example information. If the output doesn't match, then a DocTestFailure is raised: >>> test = DocTestParser().get_doctest(''' ... >>> x = 1 ... >>> x ... 2 ... ''', {}, 'foo', 'foo.py', 0) >>> try: ... runner.run(test) ... except DocTestFailure as f: ... failure = f DocTestFailure objects provide access to the test: >>> failure.test is test True As well as to the example: >>> failure.example.want '2\n' and the actual output: >>> failure.got '1\n' If a failure or error occurs, the globals are left intact: >>> del test.globs['__builtins__'] >>> test.globs {'x': 1} >>> test = DocTestParser().get_doctest(''' ... >>> x = 2 ... >>> raise KeyError ... ''', {}, 'foo', 'foo.py', 0) >>> runner.run(test) Traceback (most recent call last): ... doctest.UnexpectedException: <DocTest foo from foo.py:0 (2 examples)> >>> del test.globs['__builtins__'] >>> test.globs {'x': 2} But the globals are cleared if there is no error: >>> test = DocTestParser().get_doctest(''' ... >>> x = 2 ... ''', {}, 'foo', 'foo.py', 0) >>> runner.run(test) TestResults(failed=0, attempted=1) >>> test.globs {} NTc C s$ t | |||d}|r |j |S )NF)r rR r1 rM )rj r r2 r rQ rr, r, r- rR 3 s zDebugRunner.runc C s t |||d S rl )r r( r, r, r- r) 9 s z'DebugRunner.report_unexpected_exceptionc C s t |||d S rl )r r# r, r, r- r' < s zDebugRunner.report_failure)NNT)r6 rp rq r rR r) r' r, r, r, r- r s Z TFc C s | dkrt jd} t| s,td| f |dkr:| j}t|d} |rVt||d} n t ||d} | j | |||dD ]} | | qt|r| t dkr| a n t | t| j| jS )a* m=None, name=None, globs=None, verbose=None, report=True, optionflags=0, extraglobs=None, raise_on_error=False, exclude_empty=False Test examples in docstrings in functions and classes reachable from module m (or the current module if m is not supplied), starting with m.__doc__. Also test examples reachable from dict m.__test__ if it exists and is not None. m.__test__ maps names to functions, classes and strings; function and class docstrings are tested even if the name is private; strings are tested directly, as if they were docstrings. Return (#failures, #tests). See help(doctest) for an overview. Optional keyword arg "name" gives the name of the module; by default use m.__name__. Optional keyword arg "globs" gives a dict to be used as the globals when executing examples; by default, use m.__dict__. A copy of this dict is actually used for each docstring, so that each docstring's examples start with a clean slate. Optional keyword arg "extraglobs" gives a dictionary that should be merged into the globals that are used to execute examples. By default, no extra globals are used. This is new in 2.4. Optional keyword arg "verbose" prints lots of stuff if true, prints only failures if false; by default, it's true iff "-v" is in sys.argv. Optional keyword arg "report" prints a summary at the end when true, else prints nothing at the end. In verbose mode, the summary is detailed, else very brief (in fact, empty if all tests passed). Optional keyword arg "optionflags" or's together module constants, and defaults to 0. This is new in 2.3. Possible values (see the docs for details): DONT_ACCEPT_TRUE_FOR_1 DONT_ACCEPT_BLANKLINE NORMALIZE_WHITESPACE ELLIPSIS SKIP IGNORE_EXCEPTION_DETAIL REPORT_UDIFF REPORT_CDIFF REPORT_NDIFF REPORT_ONLY_FIRST_FAILURE Optional keyword arg "raise_on_error" raises an exception on the first unexpected exception or failure. This allows failures to be post-mortem debugged. Advanced tomfoolery: testmod runs methods of a local instance of class doctest.Tester, then merges the results into (or creates) global Tester instance doctest.master. Methods of doctest.master can be called directly too, if you want to do something unusual. Passing report=0 to testmod is especially useful then, to delay displaying a summary. Invoke doctest.master.summarize(verbose) when you're done fiddling. Nr z testmod: module required; %r)r r r r1 r )r> r? r/ r7 r8 rB r6 r r r rw rR rT masterrV r% r r ) r r+ r1 r reportr r raise_on_errorr finderrunnerr r, r, r- r H s$ E c C s |r|st dt| ||| p d\} } |dkr:tj| }|dkrHi }n| }|dk rb|| d|krrd|d< | rt||d} n t||d} | | ||| d}| | |r| t dkr| a n t | t| j| jS )a Test examples in the given file. Return (#failures, #tests). Optional keyword arg "module_relative" specifies how filenames should be interpreted: - If "module_relative" is True (the default), then "filename" specifies a module-relative path. By default, this path is relative to the calling module's directory; but if the "package" argument is specified, then it is relative to that package. To ensure os-independence, "filename" should use "/" characters to separate path segments, and should not be an absolute path (i.e., it may not begin with "/"). - If "module_relative" is False, then "filename" specifies an os-specific path. The path may be absolute or relative (to the current working directory). Optional keyword arg "name" gives the name of the test; by default use the file's basename. Optional keyword argument "package" is a Python package or the name of a Python package whose directory should be used as the base directory for a module relative filename. If no package is specified, then the calling module's directory is used as the base directory for module relative filenames. It is an error to specify "package" if "module_relative" is False. Optional keyword arg "globs" gives a dict to be used as the globals when executing examples; by default, use {}. A copy of this dict is actually used for each docstring, so that each docstring's examples start with a clean slate. Optional keyword arg "extraglobs" gives a dictionary that should be merged into the globals that are used to execute examples. By default, no extra globals are used. Optional keyword arg "verbose" prints lots of stuff if true, prints only failures if false; by default, it's true iff "-v" is in sys.argv. Optional keyword arg "report" prints a summary at the end when true, else prints nothing at the end. In verbose mode, the summary is detailed, else very brief (in fact, empty if all tests passed). Optional keyword arg "optionflags" or's together module constants, and defaults to 0. Possible values (see the docs for details): DONT_ACCEPT_TRUE_FOR_1 DONT_ACCEPT_BLANKLINE NORMALIZE_WHITESPACE ELLIPSIS SKIP IGNORE_EXCEPTION_DETAIL REPORT_UDIFF REPORT_CDIFF REPORT_NDIFF REPORT_ONLY_FIRST_FAILURE Optional keyword arg "raise_on_error" raises an exception on the first unexpected exception or failure. This allows failures to be post-mortem debugged. Optional keyword arg "parser" specifies a DocTestParser (or subclass) that should be used to extract tests from the files. Optional keyword arg "encoding" specifies an encoding that should be used to convert the file to unicode. Advanced tomfoolery: testmod runs methods of a local instance of class doctest.Tester, then merges the results into (or creates) global Tester instance doctest.master. Methods of doctest.master can be called directly too, if you want to do something unusual. Passing report=0 to testmod is especially useful then, to delay displaying a summary. Invoke doctest.master.summarize(verbose) when you're done fiddling. 8Package may only be specified for module-relative paths.rA Nr6 r rd r" )r rX r r basenamer r r r r rR rT rf rV r% r r )rT rV r+ rU r1 r rg r r rh r rN textrj r r, r, r- r s2 R NoNamec C s@ t |dd}t||d}|j| ||dD ]}|j||d q(dS )ar Test examples in the given object's docstring (`f`), using `globs` as globals. Optional argument `name` is used in failure messages. If the optional argument `verbose` is true, then generate output even if there are no failures. `compileflags` gives the set of flags that should be used by the Python compiler when running the examples. If not specified, then it will default to the set of future-import flags that apply to `globs`. Optional keyword arg `optionflags` specifies options for the testing and output. See the documentation for `testmod` for more information. F)r r rd )r1 )r2 N)r r rw rR ) rW r1 r r+ r2 r ri rj r r, r, r- r + s c C s" | t @ | krtd| t}| a|S )a? Sets the unittest option flags. The old flag is returned so that a runner could restore the old value if it wished to: >>> import doctest >>> old = doctest._unittest_reportflags >>> doctest.set_unittest_reportflags(REPORT_NDIFF | ... REPORT_ONLY_FIRST_FAILURE) == old True >>> doctest._unittest_reportflags == (REPORT_NDIFF | ... REPORT_ONLY_FIRST_FAILURE) True Only reporting flags can be set: >>> doctest.set_unittest_reportflags(ELLIPSIS) Traceback (most recent call last): ... ValueError: ('Only reporting flags allowed', 8) >>> doctest.set_unittest_reportflags(old) == (REPORT_NDIFF | ... REPORT_ONLY_FIRST_FAILURE) True z Only reporting flags allowed)r r _unittest_reportflags)r2 oldr, r, r- r H s c @ sl e Zd ZdddZdd Zdd Zd d Zd d Zd d Zdd Z dd Z dd Z dd Z e jZdd ZdS ) DocTestCaser" Nc C s. t j| || _|| _|| _|| _|| _d S rl )unittestTestCaser _dt_optionflags _dt_checker_dt_test _dt_setUp _dt_tearDown)rj r r setUptearDownr r, r, r- r n s zDocTestCase.__init__c C s | j }| jd k r| | d S rl )rv rw rj r r, r, r- ry x s zDocTestCase.setUpc C s( | j }| jd k r| | |j d S rl )rv rx r1 rM r{ r, r, r- rz ~ s zDocTestCase.tearDownc C s~ | j }tj}t }| j}|t@ s(|tO }t|| jdd}z d|_ |j ||j dd\}}W 5 |t_X |rz| | | d S )NFr r r zF----------------------------------------------------------------------)r rQ )rv r> r r# rt r ro r ru r+ rR rD ZfailureExceptionformat_failurerc )rj r rp newr rj r r r, r, r- runTest s( zDocTestCase.runTestc C sP | j }|jd krd}n d|j }d|jddd }d|j|j|||f S )Nzunknown line numberz%sr rr z:Failed doctest test for %s File "%s", line %s, in %s %s)rv r r r+ rt rT )rj errr r Zlnamer, r, r- r} s zDocTestCase.format_failurec C s6 | t| j| jdd}|j| jdd | dS )a Run the test case without results and without catching exceptions The unit test framework includes a debug method on test cases and test suites to support post-mortem debugging. The test code is run in such a way that errors are not caught. This way a caller can catch the errors and initiate post-mortem debugging. The DocTestCase provides a debug method that raises UnexpectedException errors if there is an unexpected exception: >>> test = DocTestParser().get_doctest('>>> raise KeyError\n42', ... {}, 'foo', 'foo.py', 0) >>> case = DocTestCase(test) >>> try: ... case.debug() ... except UnexpectedException as f: ... failure = f The UnexpectedException contains the test, the example, and the original exception: >>> failure.test is test True >>> failure.example.want '42\n' >>> exc_info = failure.exc_info >>> raise exc_info[1] # Already has the traceback Traceback (most recent call last): ... KeyError If the output doesn't match, then a DocTestFailure is raised: >>> test = DocTestParser().get_doctest(''' ... >>> x = 1 ... >>> x ... 2 ... ''', {}, 'foo', 'foo.py', 0) >>> case = DocTestCase(test) >>> try: ... case.debug() ... except DocTestFailure as f: ... failure = f DocTestFailure objects provide access to the test: >>> failure.test is test True As well as to the example: >>> failure.example.want '2\n' and the actual output: >>> failure.got '1\n' Fr| )rQ N)ry r rt ru rR rv rz )rj rj r, r, r- r! s B zDocTestCase.debugc C s | j jS rl rv r+ r r, r, r- r s zDocTestCase.idc C sP t | t |k rtS | j|jkoN| j|jkoN| j|jkoN| j|jkoN| j|jkS rl )r r rv rt rw rx ru r r, r, r- r s zDocTestCase.__eq__c C s t | j| j| j| jfS rl )r rt rw rx ru r r, r, r- r s zDocTestCase.__hash__c C s, | j jd}d|d d|d d f S )Nr z%s (%s)rr )rv r+ rt r )rj r+ r, r, r- r s zDocTestCase.__repr__c C s d| j j S )Nz Doctest: r r r, r, r- shortDescription s z DocTestCase.shortDescription)r" NNN)r6 rp rq r ry rz r r} r! r r r r r ra r r, r, r, r- rq l s H rq c @ s0 e Zd Zdd Zdd Zdd Zdd ZeZd S ) SkipDocTestCasec C s || _ t| d d S rl )rC rq r )rj rC r, r, r- r s zSkipDocTestCase.__init__c C s | d d S )Nz-DocTestSuite will not work with -O2 and above)ZskipTestr r, r, r- ry s zSkipDocTestCase.setUpc C s d S rl r, r r, r, r- test_skip s zSkipDocTestCase.test_skipc C s d| j j S )NzSkipping tests from %s)rC r6 r r, r, r- r s z SkipDocTestCase.shortDescriptionN)r6 rp rq r ry r r ra r, r, r, r- r s r c @ s e Zd Zdd ZdS ) _DocTestSuitec C s d S rl r, )rj indexr, r, r- _removeTestAtIndex s z _DocTestSuite._removeTestAtIndexN)r6 rp rq r r, r, r, r- r s r c K s |dkrt }t| } |j| ||d}|sNtjjdkrNt }|t| |S | t }|D ]T}t |j dkrtq`|j s| j }|dd dkr|dd }||_ |t|f| q`|S )a Convert doctest tests for a module to a unittest test suite. This converts each documentation string in a module that contains doctest tests to a unittest test case. If any of the tests in a doc string fail, then the test case fails. An exception is raised showing the name of the file containing the test and a (sometimes approximate) line number. The `module` argument provides the module to be tested. The argument can be either a module or a module name. If no argument is given, the calling module is used. A number of options may be provided as keyword arguments: setUp A set-up function. This is called before running the tests in each file. The setUp function will be passed a DocTest object. The setUp function can access the test globals as the globs attribute of the test passed. tearDown A tear-down function. This is called after running the tests in each file. The tearDown function will be passed a DocTest object. The tearDown function can access the test globals as the globs attribute of the test passed. globs A dictionary containing initial global variables for the tests. optionflags A set of doctest option flags expressed as an integer. Nre r4 r" r r rr )r rD rw r> r2 optimizer addTestr r r) r rT r rq ) rC r1 r Z test_finderr r suiter rT r, r, r- r # s( % c @ s$ e Zd Zdd Zdd Zdd ZdS ) DocFileCasec C s d | jjdS )NrO r )r rv r+ rt r r, r, r- r e s zDocFileCase.idc C s | j jS rl )rv rT r r, r, r- r h s zDocFileCase.__repr__c C s d| j j| j j|f S )Nz2Failed doctest test for %s File "%s", line 0 %s)rv r+ rT )rj r r, r, r- r} k s zDocFileCase.format_failureN)r6 rp rq r r r} r, r, r, r- r c s r c K sv |d kri }n| }|r&|s&tdt| |||p4d\}} d|krL| |d< tj| }||||| d} t| f|S )Nrk rA r r" )r r rX r r rl r r ) r rV rU r1 r rN r docr+ r r, r, r- DocFileTestp s r c O sD t }|ddr$t|d|d< | D ]}|t|f| q(|S )a A unittest suite for one or more doctest files. The path to each doctest file is given as a string; the interpretation of that string depends on the keyword argument "module_relative". A number of options may be provided as keyword arguments: module_relative If "module_relative" is True, then the given file paths are interpreted as os-independent module-relative paths. By default, these paths are relative to the calling module's directory; but if the "package" argument is specified, then they are relative to that package. To ensure os-independence, "filename" should use "/" characters to separate path segments, and may not be an absolute path (i.e., it may not begin with "/"). If "module_relative" is False, then the given file paths are interpreted as os-specific paths. These paths may be absolute or relative (to the current working directory). package A Python package or the name of a Python package whose directory should be used as the base directory for module relative paths. If "package" is not specified, then the calling module's directory is used as the base directory for module relative filenames. It is an error to specify "package" if "module_relative" is False. setUp A set-up function. This is called before running the tests in each file. The setUp function will be passed a DocTest object. The setUp function can access the test globals as the globs attribute of the test passed. tearDown A tear-down function. This is called after running the tests in each file. The tearDown function will be passed a DocTest object. The tearDown function can access the test globals as the globs attribute of the test passed. globs A dictionary containing initial global variables for the tests. optionflags A set of doctest option flags expressed as an integer. parser A DocTestParser (or subclass) that should be used to extract tests from the files. encoding An encoding that will be used to convert the files to unicode. rV TrU )r r/ rD r r )pathskwr r r, r, r- r s 8 c C s g }t | D ]x}t|trh||jdd |j}|r|d |dd |ddd D 7 }q|dd |ddd D 7 }q|r|d dkr| q|r|d dkr|d qd |d S ) aw Extract script from text with examples. Converts text with examples to a Python script. Example input is converted to regular code. Example output and all other words are converted to comments: >>> text = ''' ... Here are examples of simple math. ... ... Python has super accurate integer addition ... ... >>> 2 + 2 ... 5 ... ... And very friendly error messages: ... ... >>> 1/0 ... To Infinity ... And ... Beyond ... ... You can use logic if you want: ... ... >>> if 0: ... ... blah ... ... blah ... ... ... ... Ho hum ... ''' >>> print(script_from_examples(text)) # Here are examples of simple math. # # Python has super accurate integer addition # 2 + 2 # Expected: ## 5 # # And very friendly error messages: # 1/0 # Expected: ## To Infinity ## And ## Beyond # # You can use logic if you want: # if 0: blah blah # # Ho hum <BLANKLINE> Nrr z # Expected:c S s g | ] }d | qS )z## r, r r, r, r- r s z(script_from_examples.<locals>.<listcomp>rF c S s g | ] }t |qS r, )r r r, r, r- r s r~ r" ) r r r9 r r r rx rt popr )r] r Zpiecerx r, r, r- r s : " c sJ t | } t | } fdd|D }|s4t d|d }t|j}|S )a Extract the test sources from a doctest docstring as a script. Provide the module (or dotted name of the module) containing the test to be debugged and the name (within the module) of the object with the doc string with tests to be debugged. c s g | ]}|j kr|qS r, r* )r r7 r* r, r- r . s z testsource.<locals>.<listcomp>znot found in testsr" )rD r rw r r r )rC r+ r r testsrcr, r* r- r % s c C s t | }t||| dS )z4Debug a single doctest docstring, in argument `src`'N)r debug_script)srcpmr1 r r, r, r- r 5 s c C s ddl }|r| }ni }|rvzt| || W q tt d |jdd}| |dt d Y qX n|jdd d| || dS )z7Debug a test script. `src` is the script, as a string.r" Nr& T)r r4 zexec(%r)) r r r- r r> rd r rH Z interactionrR )r r r1 r pr, r, r- r : s r c C s$ t | } t| |}t||| j dS )zDebug a single doctest docstring. Provide the module (or dotted name of the module) containing the test to be debugged and the name (within the module) of the object with the docstring with tests to be debugged. N)rD r r r )rC r+ r r r, r, r- r! N s c @ s( e Zd ZdZdd Zdd Zdd ZdS ) _TestClassz A pointless class, for sanity-checking of docstring testing. Methods: square() get() >>> _TestClass(13).get() + _TestClass(-12).get() 1 >>> hex(_TestClass(13).square().get()) '0xa9' c C s || _ dS )zval -> _TestClass object with associated value val. >>> t = _TestClass(123) >>> print(t.get()) 123 Nr )rj r r, r, r- r j s z_TestClass.__init__c C s | j d | _ | S )zosquare() -> square TestClass's associated value >>> _TestClass(13).square().get() 169 r4 r r r, r, r- squaret s z_TestClass.squarec C s | j S )z~get() -> return TestClass's associated value. >>> x = _TestClass(-42) >>> print(x.get()) -42 r r r, r, r- r/ ~ s z_TestClass.getN)r6 rp rq r r r r/ r, r, r, r- r \ s r z Example of a string object, searched as-is. >>> x = 1; y = 2 >>> x + y, x * y (3, 2) a In 2.2, boolean expressions displayed 0 or 1. By default, we still accept them. This can be disabled by passing DONT_ACCEPT_TRUE_FOR_1 to the new optionflags argument. >>> 4 == 4 1 >>> 4 == 4 True >>> 4 > 4 0 >>> 4 > 4 False z Blank lines can be marked with <BLANKLINE>: >>> print('foo\n\nbar\n') foo <BLANKLINE> bar <BLANKLINE> z If the ellipsis flag is used, then '...' can be used to elide substrings in the desired output: >>> print(list(range(1000))) #doctest: +ELLIPSIS [0, 1, 2, ..., 999] a If the whitespace normalization flag is used, then differences in whitespace are ignored. >>> print(list(range(30))) #doctest: +NORMALIZE_WHITESPACE [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29] )r r zbool-int equivalencez blank linesZellipsiszwhitespace normalizationc C s" dd l } | jdd}|jdddddd |jd d d t g d d |jddddd |jdddd | }|j}|j}d}|jD ]}|t| O }q|j r|t O }|D ]v}| drt j |\}}tj d| t|d d } tj d= t| ||d\} } nt|d||d\} } | r dS qdS ) Nr" zdoctest runner)Z descriptionr z --verbose store_trueFz'print very verbose output for all tests)actiondefaulthelpz-oz--optionr zqspecify a doctest option flag to apply to the test run; may be specified more than once to apply multiple options)r choicesr r z-fz --fail-fastzystop running tests after first failure (this is a shorthand for -o FAIL_FAST, and is in addition to any other -o options))r r r` r z file containing the tests to run)nargsr z.pyrd )rV r r r& )argparseArgumentParser add_argumentr' keys parse_argsr` r r Z fail_fastr ri r r rt r> insertr; r r ) r r r Z testfilesr r r rT dirnamer r rO r, r, r- _test sL r r )r4 )rY ) NNNNTr" NFF)Frn Nr" )NNNN)FN)FN)F)Sr Z __docformat____all__r. r^ r7 r r r r[ r> ra rr ior# collectionsr$ r% r' r r r r r r r r r r r r r r rZ rs r3 rD rJ rX r_ rf rg r} r r r r rO r r r r r r Exceptionr r r rf r r r ro r rs rq r Z TestSuiter r r r r r r r r r! r r r r6 exitr, r, r, r- <module> sF '- 1%.DK l < ; n h { $ ! @ IR , 3-
Simpan