grthtrhthjhtyjytjytkergtrhtrjytjerhrfh4:24 29/09/2026+  vRtRt.RNRNRNRNRNRNRNR NR NR NR NR NRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNRNR NR!NR"Nt^R#It^R#It^R#It^R#It^R#It^R#It^R#I t ^R#I t ^R#I t ^R#I t ^R#I t ^R$IHtHt^R%IHt^R#It^R&IHtHtR't!R(R)]!R)R*44t/tR+t]!R4t]!R4t]!R4t]!R4t]!R4t]!R4t]],],],],],t ]!R 4t!]!R 4t"]!R 4t#]!R 4t$]!R4t%]!]",]#,]$,]%,t&R,t'R-t(R.t)RjR/lt*R0t+R1t,RkR2lt-R3t.!R4R5]4t/R6t0R7t1R8t2!R9R:] Pf4t4R;t5!R<R4t6!R=R4t7!R>R4t8!R?R4t9!R@R4t:RARBlt;!RCR4t<!RDR]=4t>!RER]=4t?!RFR]:4t@R#sARlRHltBR'R#R#R#R#R'^R#RG]8!4R#3 RIltCRmRJltD^sERKtF!RLRM] P4tH!RNRO]H4tI!RPRQ] P4tKRnRRltL!RSRT]H4tMR'R#R#]8!4R#3RUltNRVtORWtPRXtQRoRYltRRoRZltSRpR[ltT!R\R]4tUR]]UR^R_R`RaRbRcRdReRfRg/tVRhtW]XRi8Xd] P!]W!44R##R##)qaModule 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_srcdebugN)StringIOIncrementalNewlineDecoder) namedtuple) ANSIColors can_colorizeTcFaa]tRt^rtoR^/V3RlltV3RltRtVtV;t#) TestResultsskippedc4<\SV`WV4pW4nV#N)super__new__r*)clsfailed attemptedr*results __class__s&&&$ ./opt/alt/python314/lib64/python3.14/doctest.pyr.TestResults.__new__ss'/#y9!c<VP'd+RVP RVP RVP R2#\SV`4#)zTestResults(failed=z , attempted=z , skipped=))r*r0r1r-__repr__)selfr3s&r4r9TestResults.__repr__xsP <<<)$++7!!% 01#||nA/ 0 7#% %r6) __name__ __module__ __qualname____firstlineno__r.r9__static_attributes____classdictcell__ __classcell__)r3 __classdict__s@@r4r)r)rs1 &&r6r)zfailed attemptedcV\PV^\\4,4#))OPTIONFLAGS_BY_NAME setdefaultlen)names&r4rrs  ) )$S9L5M0M NNr6z z...c^p\PF=pVPVR4pV\\V4JgK+WP,pK? V#)zy Return the compiler-flags associated with the future features that have been imported into the given namespace (globs). N) __future__all_feature_namesgetgetattr compiler_flag)globsflagsfnamefeatures& r4_extract_future_flagsrUsM E--))E4( gj%0 0 ** *E. Lr6c\P!V4'dV#\V\4'd \ V\ 4\ 4R.4#Vf.\P\P!V4,#\R4h \d@\P\P!T4PR,,u#i;i \dR#i;i)ag 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. *Nr=z"Expected a module, string, or None)inspectismodule isinstancestr __import__globalslocalssysmodules_getframemodulenameAttributeError _getframe f_globalsKeyError TypeError)moduledepths&&r4_normalize_moduleris FC &')VXu==   O{{3#:#:5#ABB <== " O{{3==#7#A#A*#MNN O   s+*BACCCC C,+C,c:\RR4PVR4#)NT)r$decode)datas&r4_newline_convertrms $T4 0 7 7d CCr6cV'd\V^4p\W4p\VRR4;pfVPPp\ VR4'd0VPV4pVPV4p\V4V3#\WR7;_uu_4pVP4V3uuRRR4# \ dLi;i +'giR#;i) __loader__Nget_data)encoding) ri_module_relative_pathrO__spec__loaderrbhasattrrqrkrmopenread)filenamepackagemodule_relativerrru file_contentsfs&&&& r4_load_testfiler~s#GQ/(;g|T: :F C  ))00 6: & &"OOH5M)00:M$M2H< < h * *avvx! + *"   + * *sB:C : CC C c@\P!RVR,V4#)zr Add the given number of space characters to the beginning of every non-blank line in `s`, and return the result. z (?m)^(?!$) )resub)sindents&&r4_indentrs 66,s A ..r6cp\4pVwr#p\P!W#WAR7VP4#)zn Return a string containing a traceback message for the given exc_info tuple (as returned by sys.exc_info()). )file)r# tracebackprint_exceptiongetvalue)exc_infoexcoutexc_typeexc_valexc_tbs& r4_exception_tracebackrs2 ZF (Hv hE ?? r6c0a]tRtRtoRtRRltRtVtR#) _SpoofOutic\P!V4pV'd!VPR4'g VR, pV#) )r#rendswith)r:results& r4r_SpoofOut.getvalues3""4( &//$// dNF r6NcTVPV4\P!V4R#r,)seekr#truncate)r:sizes&&r4r_SpoofOut.truncate%s $$r6r<r,)r=r>r?r@rrrArBrDs@r4rrs  r6rc\V9dW8H#VP\4p^\V4rCV^,pV'd)VPV4'd\V4pV^MR#VR,pV'd0VP V4'dV\V4,pVRMR#W48dR#VF1pVP WSV4pV^8dR#V\V4, pK3 R#)zO Essentially the only subtle case: >>> _ellipsis_match('aa...aa', 'aaa') False FT)ELLIPSIS_MARKERsplitrI startswithrfind)wantgotwsstartposendposws&& r4_ellipsis_matchr*s d"{ O $B#c(f 1A >>!  1vH1 2A <<?? c!f F2 88A0 a<CF r6cHVP4pV'd RV,#R#)z)Return a commented form of the given linez# #)rstrip)lines&r4 _comment_liner[s ;;=D Dyr6c^\V4r!VPR4pV^8dTpVPR^V4pV^8dTpVPR^V4pV^8d V^,pWV#)r:.)rIrrfind)msgstartendis& r4_strip_exception_detailsrcsrCH3 AAv aAAv #q#AAv! c?r6cHa]tRtRtoRtRtR RR/RlltRtRtR t Vt R#) _OutputRedirectingPdbi}z 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. cpWnRVn\PP WRR7^VnR#)FT)stdoutnosigintN)_OutputRedirectingPdb__out$_OutputRedirectingPdb__debugger_usedpdbPdb__init__ use_rawinput)r:outs&&r4r_OutputRedirectingPdb.__init__s. $ D9r6NcommandscRVnVf \P!4Pp\P P WVR7R#)TN)r)rr_rcf_backrr set_trace)r:framers&&$r4r_OutputRedirectingPdb.set_traces7# =MMO**E $9r6clVP'd"\PPV4R#R#r,)rrr set_continuer:s&r4r"_OutputRedirectingPdb.set_continues'     GG  & r6c\PpVP\n\PP !V.VO5!V\n# T\ni;ir,)r_rrrrtrace_dispatch)r:args save_stdouts&* r4r$_OutputRedirectingPdb.trace_dispatchsAjj ZZ  %77))$66$CJCJs !A A!)__debugger_used__outrr,) r=r>r?r@__doc__rrrrrArBrs@r4rr}s* :: ' %%r6rc\P!V4'g\RV,4hVPR4'd \ R4h\ P P!VPR4!p\VR4'd3\ P PVP4^,pEM!VPR8Xd\\P4^8dY\P^,R8wd=\ P P\P^,4^,pM\ PpM\VR4'd\VP FKp\ P PW14p\ P P#V4'gKIVu# \ RVP,4h\ P PW!4#)zExpected a module: %r/z1Module-relative files may not have absolute paths__file____main____path__zBCan't resolve paths relative to the module %r (it has no __file__))rXrYrfr ValueErrorospathjoinrrvrr=rIr_argvcurdirrexists)rg test_pathbasedir directoryfullpaths&& r4rsrssT   F # #/&899C  LMM ys35Ivz""''--03 J & sxx=?sxx{b0ggmmCHHQK03GiiG 6: & &#__ 77<< =77>>(++#O- 3!??+, , 77<< ++r6c:a]tRtRtoRtRRltRtRtRtVt R#) ria 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. Nc2VPR4'g VR, pV'd!VPR4'g VR, pVe!VPR4'g VR, pWnW nW@nWPnVf/pW`nW0nR#)rN)rsourcerlinenoroptionsexc_msg)r:rrrrrrs&&&&&&&r4rExample.__init__s|t$$ dNF  d++ DLD  w'7'7'='= tOG    ?bG  r6c\V4\V4Jd\#VPVP8H;'dVPVP8H;'d}VPVP8H;'d\VP VP 8H;'d;VP VP 8H;'dVPVP8H#r,)typeNotImplementedrrrrrrr:others&&r4__eq__Example.__eq__s :T%[ (! !{{ell*--yyEJJ&--{{ell*--{{ell*--||u}}, -- ||u}},  -r6c\VPVPVPVPVP 34#r,)hashrrrrrrs&r4__hash__Example.__hash__s3T[[$))T[[$++\\#$ $r6)rrrrrr)NrrN) r=r>r?r@rrrrrArBrs@r4rrs!D$ -$$r6cBa]tRtRtoRtRtRtRtRtRt Rt Vt R #) ria% 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 lWnW`nVP4VnW0nW@nWPnR#)zt Create a new DocTest containing the given examples. The DocTest's globals are initialized with a copy of `globs`. N)examples docstringcopyrQrJryr)r:rrQrJryrrs&&&&&&&r4rDocTest.__init__,s*! "ZZ\    r6c @\VP4^8XdRpM9\VP4^8XdRpMR\VP4,pRVPP: RVP: RVP : RVP : RV: R 2 #) rz no examplesz 1 examplez %d examples)rIrr3r=rJryr)r:rs& r4r9DocTest.__repr__:sp t}}  "$H  1 $"H$s4=='99H((DMM4;;B Cr6c\V4\V4Jd\#VPVP8H;'dVPVP8H;'d}VPVP8H;'d\VP VP 8H;'d;VP VP 8H;'dVPVP8H#r,)rrrrrQrJryrrs&&r4rDocTest.__eq__Es :T%[ (! !}}.++~~0++zzU[[(++yyEJJ&++}}. ++ {{ell*  +r6cp\VPVPVPVP34#r,)rrrJryrrs&r4rDocTest.__hash__Ps&T^^TYY t{{KLLr6c8\V\4'g\#VPe VPMRpVPe VPMRpVPVP V\ V43VPVP V\ V438#)Nr)rZrrrrJryid)r:rself_lno other_lnos&& r4__lt__DocTest.__lt__Tsy%))! !"&++"94;;r$)LL$U^^Y5 BC Dr6)rrryrQrrJN) r=r>r?r@rrr9rrrrArBrs@r4rrs,.  C +MDDr6ca]tRtRtoRt]P !R]P]P,4t ]P !R]P]P,]P,4t ]P !R4Pt RRltRtRRltR t]P !R ]P4tR t]P !R ]P4tR tRtRtRtVtR#)riaz< A class used to parse strings containing doctest examples. a # Source consists of a PS1 line followed by zero or more PS2 lines. (?P (?:^(?P [ ]*) >>> .*) # PS1 line (?:\n [ ]* \.\.\. .*)*) # PS2 lines \n? # Want consists of any non-blank lines that do not start with PS1. (?P (?:(?![ ]*$) # 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 Traceback\ \( (?: most\ recent\ call\ last | innermost\ last ) \) : ) \s* $ # toss trailing whitespace on the header. (?P .*?) # don't blink: absorb stuff until... ^ (?P \w+ .*) # a line *starts* with alphanum. z ^[ ]*(#.*)?$c $VP4pVPV4pV^8d3RPVPR4Uu.uFqDVRNK up4p.p^^rvVPP V4FpVP WVP44WqPRWhP44, pVPWV4wrrVPV 4'g?VP \WV VV\VPR44,V R74WqPRVP4VP44, pVP4pK VP WR4V#uupi)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. rNr)rrr) expandtabs _min_indentrr _EXAMPLE_REfinditerappendrcount_parse_example_IS_BLANK_OR_COMMENTrrIgroupr) r:stringrJ min_indentloutputcharnormrrrrs &&& r4parseDocTestParser.parsesX""$%%f- >YY T8JK8J1*+8JKLFA!!**62A MM& 2 3 ll4; ;F((&9 -Vd,,V44 wvW+1+5c!''(:K6L+L,3 57 ll4AEEG<  ::f3+3aa)3+ ++s::c  :\VPR44pVPR4PR4pVPWTW#4VP VR,RV,R,W#4RP VUu.uFqfV^,RNK up4pVPR4pVPR4p \V 4^8d(\ P!R V R ,4'dV R VP V RV,VV\V4,4RP V U u.uFqVRNK up 4pVPPV4pV'dVPR 4p MRp VPWrV4p W|W3#uupiuup i) 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. rrrrFNNrrNrz *$rr) rIrr_check_prompt_blank _check_prefixrrmatch _EXCEPTION_RE _find_options) r:r rJrr source_linesslrr want_lineswlrrs &&&& r4rDocTestParser._parse_exampleshQWWX&'wwx(..t4    tD <+SZ#-=tLLALbvaxyMLAB wwvZZ% z?Q 288FJrN#C#C2 :s6z4!C $55 7yy ; "VW+ ;<    $ $T * ggenGG$$V6:--/B??+6":6!'c!1 )< t0088$dF45 5r6z ^([ ]*)(?=\S)c VPPV4Uu.uFp\V4NK pp\V4^8d \V4#^#uupi)z;Return the minimum indentation of any non-blank line in `s`) _INDENT_REfindallrImin)r:rrindentss&& r4rDocTestParser._min_indent&sJ-1__-D-DQ-GH-G63v;-GH w "((1**d"&fQh"7"?@@(r6c  \V4FJwrVV'gKVPV4'dK(\RWE,^,: RV: RV: 24h R#)zv Check that every line in the given list starts with the given prefix; if any line does not, then raise a ValueError. r8rGz& has inconsistent leading whitespace: N)rHrr)r:rIprefixrJrrrs&&&&& r4r-DocTestParser._check_prefix<sI !'GAtDOOF33 "((1**dD":;;(r6r<N)z)r=r>r?r@rrcompile MULTILINEVERBOSErDOTALLr/r.rr!r%r$rr:r0rArr,r-rArBrs@r4rras**  \\BJJ & (K,JJ ZZ",, & 2 4M::o6<<%N 7 +*.f::&D&(ll48,bll;J @ ; ;r6cha]tRtRtoRtR]!4RR3RltRRltRtR t R t R t R t R t VtR#)riLa$ 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 6W nWnW0nW@nR#)a 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)r:verboseparserrecurse exclude_emptys&&&&&r4rDocTestFinder.__init__Us"   +r6Nc  Vf*\VRR4pVf\R\V4: 24hVRJdRpMVf\P!V4p\P !V4pV'g1\P !V4pV^,VRR,R8XgRpVfRpMEVe"\P!WcP4pM\P!V4pV'gRpVf#Vf/pM+VPP4pMVP4pVeVPV4RV9dRVR&.pVPWW#Wt/4VP4V# \dRpLi;i)a 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 {}. Nr=zHDocTestFinder.find: name must be given when obj.__name__ doesn't exist: Fz<]>r)rOrrrX getmodule getsourcefilegetfile linecachegetlines__dict__rfrupdate_findsort) r:objrJrgrQ extraglobsrr1testss &&&&&& r4rDocTestFinder.findkspH <3 D1D| "&s)".// U?F ^&&s+F  (((-Ds+AwtBCy(E1$4|# %$-#5#5dOO#LL$-#5#5d#;L##'L =~,,.JJLE  ! LL $ U " *E*  5t\"E   Y L sE++ E;:E;c VfR#\P!V4eV\P!V4J#\P!V4'dVPVPJ#\P !V4'g\P !V4'dZ\VR4'dVPPpM!\VR4'dVPpMR#VPV8H#\P!V4'dVPVP8H#\VR4'dVPVP8H#\V\4'dR#\R4h)zA Return true if the given object is defined in the given module. T __objclass__r>z"object must be a class or function)rXr_ isfunctionrd __globals__ismethoddescriptorismethodwrapperrvrmr>r=isclassrZpropertyr)r:rgobjectobj_mods&&& r4 _from_moduleDocTestFinder._from_modules% >   v & 2W..v66 6    ' '??f&8&88 8((00%%f--v~.. --88.. ++??g- - __V $ $??f&7&77 7 V\ * *??f&7&77 7  ) )AB Br6c Tp\P!V4p\P!V4# \dL#i;i)z< Safely unwrap objects and determine if they are functions. )rXunwrapr isroutine)r:rh maybe_routines&& r4 _is_routineDocTestFinder._is_routinesC  #NN=9M  //   s 0 >>c  VP'd\RV,4\V4V9dR#^V\V4&VPW#WFV4pVeVP V4\ P !V4'dVP'dVPP4FpwrV: RV : 2p VPV 4'g\ P!V 4'gKCVPWJ4'gK\VPWWVWg4Kr \ P !V4'EdVP'd\VR/4P4Fwr\V \ 4'g\#R\%V 4: 24h\ P&!V 4'gg\ P!V 4'gK\ P !V 4'g/\V \ 4'g\#R\%V 4: 24hV: RV : 2p VPWWVWg4K \ P!V4'dVP'dVPP4Fwr\V \(\*34'd V P,p \ P&!V 4'g5\ P!V 4'g\V \.4'gK}VPWJ4'gKV: RV : 2p VPWWVWg4K R#R#R#)zU Find tests for the given object and any contained objects, and add them to `tests`. zFinding tests in %sNr__test__z3DocTestFinder.find: __test__ keys must be strings: z^DocTestFinder.find: __test__ values must be strings, functions, methods, classes, or modules: z .__test__.)rUprintr  _get_testrrXrYrVrditemsr|rrrvrfrOrZr[rrrz staticmethod classmethod__func__rs) r:rjrhrJrgr1rQseentestvalnamevals &&&&&&&& r4rfDocTestFinder._findsp === '$. / c7d? RW ~~c E   LL    C T]]] # 2 2 4 %)73%%c**gooc.B.B%%f22JJu7L$, !5   C T]]] 'Z < B B D !'3//$&*7m&677 ))#..'//#2F2F((--C1E1E$'+3i&233/3G< 5w  (!E ??3  DMMM # 2 2 4 cL+#>??,,C&&s++ws/C/C h//''44)-w7GJJu7L$,!5%2 r6c \V\4'dTpM?VPfRpM-VPp\V\4'g \V4pVP W4pVP 'd V'gR#VfRpM0\VRR4;'g VPpVRRR8XdVRRpVPPWdVW4# \\3dRpLi;i)z[ Return a DocTest for the given object, if it defines a docstring; otherwise, return None. Nrr.pycr) rZr[rrfrb _find_linenorWrOr=rTr%) r:rhrJrgrQr1rrrys &&&&&& r4rDocTestFinder._get_test6s c3  I ;;& "I # I%i55$' N ""35    y >Hvz48KKFOOH}&#CR=||'' $(0: :%~.   sC-CC0/C0c  Rp\VRR4p\P!V4'dVe^p\P!V4'dvVerVfR#\P !R\P !\VRR44,4p\V4F wrgVPV4'gKTpM \P!V4'd VPp\V\4'd VPp\V\P4'd VP p\P"!V4'd7\VRR4'd$\P$!V4pVP&p\P*!V4'd VP,p\P.!V4'd VP0p\P2!V4'dVP4^, pVeaVf V^,#\P !R4p\7V\9V44F$pVPW#,4'gK"Vu# R# \(dR#i;i)zv Return a line number of the given object's docstring. Returns `None` if the given object does not have a docstring. Nrz^\s*class\s*%s\br=-z(^|.*:)\s*\w*("|\'))rOrXrYrrrrNescaperHr.ismethodrrZrsfget functoolscached_propertyfuncrzry__code__rb istracebacktb_frameisframef_codeiscodeco_firstlinenorangerI)r:rhr1rrpatrrs&&& r4rDocTestFinder._find_lineno\s CD1    C Y%:F ??3  I$9#**0YYwsJ'DEFGC$\299T??F3   C  # c8 $ $((C c944 5 5((C   S ! !gc9d&C&C..%C ll   s # #3<>#  ''!+F  #ax**34CL(9:99\122!M; 1"   s? I00 I?>I?)rWrTrVrUNNNN)r=r>r?r@rrrrrvr|rfrrrArBrs@r4rrLsE %]_T,,dLC: 0;,z$:L==r6ca]tRtRtoRtRtRRltRtRtRt Rt R t R t R t ]P!R 4tRR ltRRltRRltRtRtVtR#)ria 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 TestResults instance. >>> save_colorize = _colorize.COLORIZE >>> _colorize.COLORIZE = False >>> 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 TestResults instance: >>> runner.summarize(verbose=1) 4 items passed all tests: 2 tests in _TestClass 2 tests in _TestClass.__init__ 2 tests in _TestClass.get 1 test in _TestClass.square 7 tests in 4 items. 7 passed. Test passed. TestResults(failed=0, attempted=7) The aggregated number of tried examples and failed examples is also available via the `tries`, `failures` and `skips` attributes: >>> runner.tries 7 >>> runner.failures 0 >>> runner.skips 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`. >>> _colorize.COLORIZE = save_colorize Nc T;'g \4VnVfR\P9pW nW0nW0n^Vn^Vn^Vn /Vn \4Vn R#)a 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-v) r_checkerr_rrU optionflagsoriginal_optionflagstriesfailuresskips_statsr_fakeout)r:checkerrXrs&&&&r4rDocTestRunner.__init__sb" 22=? ?chh&G &$/!    "  r6c .VP'dVP'dFV!R\VP4,R,\VP4,4R#V!R\VP4,R,4R#R#)zo 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)rUrrr)r:rrexamples&&&&r4 report_startDocTestRunner.report_startsn ===|||K''.."99"#%,W\\%:;<K''.."99)*+ r6c >VP'd V!R4R#R#)z\ Report that the given example ran successfully. (Only displays a message if verbose=True) zok N)rUr:rrrrs&&&&&r4report_successDocTestRunner.report_successs === K r6c V!VPW#4VPPW4VP4,4R#)z' Report that the given example failed. N)_failure_headerroutput_differencerrs&&&&&r4report_failureDocTestRunner.report_failures: D  / MM + +G$:J:J K L Mr6c tV!VPW#4R,\\V44,4R#)z? Report that the given example raised an unexpected exception. zException raised: N)rrrr:rrrrs&&&&&r4report_unexpected_exception)DocTestRunner.report_unexpected_exception"s6 D  / ! "$+,@,J$K L Mr6c\4'd!\P\P3MRwr4V VP V 2.pVP 'dvVP e4VP e&VP VP ,^,pMRpVPRVP : RV: RVP: 24M4VPRVP ^,: RVP: 24VPR4VPpVP\V44RPV4#) r?zFile "", line , in zLine zFailed example:r)rr) r'r&REDRESETDIVIDERryrrrJrrr)r:rrredresetrrrs&&& r4rDocTestRunner._failure_header)s2>..Z^^Z-- .h t||nUG,- ==={{&7>>+Ew~~59 JJ vtyy: ; JJ7>>!+;+;TYYG H $% 76?#yy~r6c  a^;p;rVVPp\^4wrp VPPp \ VP 4EFwrV^, pVP\ ,;'dV^8pWpnV P'dbV PP4FCwppV'dV;PV,unK)V;PV(,unKE VP\,'d V^, pKV'gVPW1V 4RVPV 3,p\\V PVRVR4VP4VP P#4RpTP.P14pTP.P3^4T pTf)T !T P4TTP4'dTpEMS\6P8!TR,!p\;T^,\<4'ddT^,P> R2T^,P@ RT^,P> R23o\CT3Rl\ T444pTTRpR PET4pT'gT\GT4, pT PHfT pM|T !T PHTTP4'dTpMUTP\J,'d9T !\MT PH4\MT4TP4'dTpTTJdT'gTPOY1T T4MUTT Jd&T'gTPQY1T T4T^, pM*TT Jd%T'gTPSY1T T4T^, pT'gEKTP\T,'gEKM WpnVPWWWV4\YWEVR 7# \$dh\&dHp\)T4TTP*P,3pTP P#4Rp?ELRp?ii;i) 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 TestResults instance. The examples are run in the namespace `test.globs`. zsingleTN:NNrrc3^<"TF"wrVPS4'gKVxK$ R#5ir,)r).0indexrexception_line_prefixess& r4 &DocTestRunner.__run..s))+BKE??+BC+Bs- -rr*)-rrr check_outputrHrr rrrrrJexecrNrrQdebuggerrKeyboardInterrupt BaseExceptionr __traceback__tb_nextrrrrrformat_exception_only issubclass SyntaxErrorr?r>nextrrrrrrrrr_DocTestRunner__record_outcomer))r:r compileflagsrrr1rrSUCCESSFAILUREBOOMcheck examplenumrquiet optionflagrryrexcroutcome formatted_ex exc_msg_indexrrs&&&& @r4__runDocTestRunner.__run@s()((9 $//!&q$ **$-T]]#; J NI%%(AA""\  4 )0)>)>)@%Z((J6(((ZK7( *A$&& !!#W5 *TYY ,CCH -WW^^Xx)4126**> **,--((*C MM " "1 %GsD,<,<==%G )>> M hqk;77 $A;334A6#A;112!HQK4L4L3MQO/+%))+4\+B)%M $0 #?L'',//99C??*"G7??GT5E5EFF%G%%(???5gooF5g>!--//#*'!''7C@G#''7C@A D44S5=?A xD,,y88a$>_%   -9c3+<+<+D+DD **,, -sA PQ7/Q70.+)\[(?P\d+)\]>$c`VPPV4pV'd|VPR4VPP8XdRVPP \ VPR44,pVPPRR7#VPW4#)rJrTkeepends) %_DocTestRunner__LINECACHE_FILENAME_REr.rrrJrintr splitlinessave_linecache_getlines)r:rymodule_globalsr rs&&& r4__patched_linecache_getlines*DocTestRunner.__patched_linecache_getliness}  ( ( . .x 8 DIINN2ii((QWW\-B)CDG>>,,d,; ;//I Ir6c 0a aWnVf\VP4p\PoVf:SP o S eS P 4R8XdSPpMV V3RlpVP\n\P!4p\Pp\S4Vn VPP4VPP\n \P VnVP$\n\P&p\P(\n\*P,pR\*nRRRR/p V F%p \.P0P3V R4W&K' VP5WV4S\nV\n \P6!V4VP"\nV\nV\*nV P94FwrV fK V \.P0V &K V'd'VPP;4^RIp RV n## S\nT\n \P6!T4TP"\nT\nT\*nT P94FwrT fK T \.P0T &K T'd'TPP;4^RIp RT nii;i)a 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-8cb<\VPSR4S4pSPV4R#)backslashreplaceN)r[encodewrite)rrrrs&r4rDocTestRunner.run..outs)AHHX/ABHMA%%a(r6cR#Fr<)rkwargss*,r4#DocTestRunner.run..sr6 PYTHON_COLORS FORCE_COLOR) rrUrQr_rrrlowerrrgettracerrrrrrbrcr*_DocTestRunner__patched_linecache_getlines displayhook__displayhook__ _colorizer'renvironpop_DocTestRunner__runsettracerclearbuiltins_)r:rrr clear_globs save_tracesave_set_tracesave_displayhooksaved_can_colorizecolor_variableskeyvaluerrrrs&&&&& @@r4runDocTestRunner.runsB(  0>#3w#>!'')]] \\^ -k:   // (1'9'9$!>> ??--&33!> *D-F"C#%::>>#t#?/B##%__ == hh  '*+>:; #DD-($ 011CE7KL#)&>KD%#qjcAAeWU2JeA3d4&HI$2  SE$,,w/ 0 Xf%&n5 628...x(2d5*D?@3A !Q&CA [Mqcht{{.C-DAF G"u^,GE7;')  UGK89waP Q $)sAJ00@E7SC%*BU6(;-}QCwO SE)   ZL UG4 5> LLr6cVPpVPP4F8wpwrEpW29d$W#,wrxp WG,pWX,pWi,pWEV3W#&K: R#r,)rr) r:rdrJrrrrrrs && r4mergeDocTestRunner.merges` KK.3ll.@.@.B *D*8Ey,-G) 6#/.AG /Cr6) rrrrUrrrrrrrrzF**********************************************************************)NNrr,NNT)r=r>r?r@rrrrrrrrrrrrNrrr"r8r<rArBrs@r4rrsv<~G$J +MM.K?Z !jj*FGJL"bKM`//r6cFV^8dQhR\\,R\/#)rrreturn)listdictr[)formats"r4 __annotate__rDsD4KCr6c<\V4pV^8XdRMRpV RV 2#)z4 Helper to pluralise the number of items in a list. rrz item)rI)rnrs& r4r+r+s* E A1f#ASaS>r6c<a]tRtRtoRtRtRtRtRtRt Vt R#) riaC A class used to check 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 :\VPRR4R4#)z- Convert string to hex-escaped ASCII string. ASCIIr)r[r)r:rs&&r4_toAsciiOutputChecker._toAsciis188G%78'BBr6c zVPV4pVPV4pW!8XdR#V\,'gW!3R8XdR#W!3R8XdR#V\,'gX\P!R\P !\ 4,RV4p\P!RRV4pW!8XdR#V\,'dGRPVP44pRPVP44pW!8XdR#V\,'d\W4'dR#R#) ae 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. Tz (?m)^%s\s*?$rz(?m)^[^\S\n]+$rF)zTrue z1 )zFalse z0 ) rJrrrrrBLANKLINE_MARKERrrrrrr:rrrs&&&&r4rOutputChecker.check_outputs mmC }}T" ;444z..z//33366/BII6F,GGd$D&&*B4C{ - - -((399;'C88DJJL)D{  ! !t))r6cV\\,\,,'gR#V\,'dR#VPR4^8;'dVPR4^8#)FTr)r r r rrNs&&&&r4_do_a_fancy_diffOutputChecker._do_a_fancy_diffsal*+*+,,  % %zz$!#;; $!(;;r6c VPpV\,'g\P!R\V4pVP WBV4'Ed!VP RR7pVP RR7pV\,'d.\P!WV^R7p\V4R,pRpMV\,'d.\P!WV^R7p\V4R,pRpMTV\,'dB\P!\PR7p \V P!WV44pR pR X,\#R P%X44,#V'd%V'dR \#V4: R \#V4: 2#V'dR\#V4,#V'dR\#V4,#R#)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)rF:rNNz#unified diff with -expected +actualz-context diff with expected followed by actual)charjunkzndiff with -expected +actualzDifferences (%s): rz Expected: zGot: zExpected: %sGot nothing zExpected nothing Got: %szExpected nothing Got nothing )rrrrrMrQrr difflib unified_diffrAr context_diffr DifferIS_CHARACTER_JUNKcomparerr) r:rrrrr3 got_linesdiffkindengines &&&& r4rOutputChecker.output_differences[||333&&*, >4r6r<N) r=r>r?r@rrJrrQrrArBrs@r4rrs%C <~<.,5,5r6c0a]tRtRtoRtRtRtRtVtR#)ri,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*WnW nW0nR#r,)rrr)r:rrrs&&&&r4rDocTestFailure.__init__7s  r6c,\VP4#r,r[rrs&r4__str__DocTestFailure.__str__<499~r6)rrrN r=r>r?r@rrrerArBrs@r4rr,s  r6c0a]tRtRtoRtRtRtRtVtR#)ri?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*WnW nW0nR#r,)rrr)r:rrrs&&&&r4rUnexpectedException.__init__Js   r6c,\VP4#r,rdrs&r4reUnexpectedException.__str__Orgr6)rrrNrhrs@r4rr?s ! r6c:a]tRtRtoRtRRltRtRtRtVt R#) riRaRun 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: >>> 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 {} Ncx\PWW#R4pV'dVPP4V#r)rr"rQr)r:rrrrrs&&&&& r4r"DebugRunner.runs.   d,U C  JJ   r6c\W#V4hr,)rrs&&&&&r4r'DebugRunner.report_unexpected_exceptions!$::r6c\W#V4hr,)rrs&&&&&r4rDebugRunner.report_failuresTC00r6r<r>) r=r>r?r@rr"rrrArBrs@r4rrRs X t ;11r6Fc 6Vf \PPR4p\P!V4'g\ RV: 24hVf VP p\VR7p V'd\W5R7p M \W5R7p V PWW&R7Fp V PV 4K V'dV P4\fV s M\PV 4\V P V P"V P$R7#)aU 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. 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. rztestmod: module required; )r[rXrrQrir)r_r`rNrXrYrfr=rrrrr"r8masterr<r)rrr) r rJrQrXreportrriraise_on_errorr[finderrunnerrs &&&&&&&&& r4rrsJ y KKOOJ '   A  !=>> |zz 7FWFwH A5 H 4I ~ V v fll KKr6c rV'dV'g \R4h\YTT ;'gR4wrVf \PP V4pVf/pMVP 4pVeVP V4RV9dRVR&V 'd\WWR7p M \WWR7p V PWW ^4pV PV4V'dV P4\fV s M\PV 4\V PV P V P"R7#)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.rr=rrwr)rr~rrbasenamerrerrr%r"r8ryr<r)rrr)ryr{rJrzrQrXrzrrir{rYrrtextr}rs&&&&&&&&&&&& r4rr+sd+, ,$H$,$7$79ND |ww) }  Z &jWFwH   d41 =D JJt  ~ V v fll KKr6c\VRR7p\W%R7pVPWVR7FpVPWR7K R#)aB 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)rXrZrw)rQ)rN)rrrr") r}rQrXrJrrr|r}rs &&&&&& r4rrs?$7E :F 7 DF A5 1 4 32r6cRV\,V8wd \RV4h\pVsV#)aSets 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 zOnly reporting flags allowed)rr_unittest_reportflags)rRolds& r4rrs/: E)7?? C! Jr6c~a]tRtRtoRRltRtRtRtRtRt R t R t R t R t ]PtR tRtVtR#) DocTestCaseiNc\PPV4W nWPnWnW0nW@nR#r,)unittestTestCaser_dt_optionflags _dt_checker_dt_test _dt_setUp _dt_tearDown)r:rrsetUptearDownrs&&&&&&r4rDocTestCase.__init__s4 ""4(*" $r6cVPpVPP4VnVPeVP V4R#R#r,)rrQr _dt_globsrr:rs& r4rDocTestCase.setUps8}}* >> % NN4  &r6cVPpVPeVPV4VPP4VPP VP 4R#r,)rrrQrrerrs& r4rDocTestCase.tearDownsM}}    (   d #  $..)r6c\VPp\Pp\4pVPpV\ ,'gV\ ,p\VVPRR7pRVn VPWPRR7pVPVP8Xd\P!R4hV\nVP 'd>VP#VP%VP'4P)R444hR# T\ni;i)FrrrX)rrzall examples were skippedrNzF----------------------------------------------------------------------)rr_rr#rrrrrrr"rr*r1rSkipTestr0failureExceptionformat_failurerr)r:rrnewrr}r2s& r4runTestDocTestCase.runTest s}}jjj** o-- 0 0K;'+'7'7H #FNjj99%jHG'"3"33''(CDD4CJ >>>''(;(;CLLN>> 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)rN)rrrrr"rr)r:r}s& r4r"DocTestCase.debug* sID )=)=%)%5%5uF 4==e 4 r6c.VPP#r,rrJrs&r4r DocTestCase.idr s}}!!!r6cx\V4\V4Jd\#VPVP8H;'d}VPVP8H;'d\VPVP8H;'d;VP VP 8H;'dVP VP 8H#r,)rrrrrrrrs&&r4rDocTestCase.__eq__u s :T%[ (! !}}.55##u'<'<<55~~055  E$6$66555#4#44  5r6cp\VPVPVPVP34#r,)rrrrrrs&r4rDocTestCase.__hash__ s3T))4>>4;L;L%%'( (r6cVPPPR4pVR,: RRPVRR4: R2#)rrNr8r)rrJrr)r:rJs& r4r9DocTestCase.__repr__ s<}}!!'', HHchhtCRy&9::r6c<RVPP,#)z Doctest: rrs&r4shortDescriptionDocTestCase.shortDescription sT]]////r6)rrrrrr)rNNN)r=r>r?r@rrrrrr"r rrr9rtrerrArBrs@r4rrsO%!*Z2 FP"5(;nnG00r6rc<a]tRtRtoRtRtRtRt]tRt Vt R#)SkipDocTestCasei c>Wn\PVR4R#r,)rgrr)r:rgs&&r4rSkipDocTestCase.__init__ s T4(r6c(VPR4R#)z-DocTestSuite will not work with -O2 and aboveN)skipTestrs&r4rSkipDocTestCase.setUp s EFr6cR#r,r<rs&r4 test_skipSkipDocTestCase.test_skip  r6c<RVPP,#)zSkipping tests from %s)rgr=rs&r4r SkipDocTestCase.shortDescription s'$++*>*>>>r6)rgN) r=r>r?r@rrrrrerArBrs@r4rr s!)G ?Gr6rc&a]tRtRtoRtRtVtR#) _DocTestSuitei cR#r,r<)r:rs&&r4_removeTestAtIndex _DocTestSuite._removeTestAtIndex rr6r<N)r=r>r?r@rrArBrs@r4rr s  r6rc Vf \4p\V4pVPWVR7pV'gF\PP ^8d'\ 4pVP\V44V#VP4\ 4pVFmp\VP4^8XdKVP'g"VPpVRRR8XdVRRpWn VP\V3/VB4Ko V#)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. Nrxrrr)rrirr_rRoptimizeraddTestrrgrIrryrr) rgrQri test_finderrrjsuiterrys &&&&, r4rr sJ#o v &F   VZ  HE SYY''!+ of-.  JJL OE t}}  " }}}H}&#CR=$M k$2'23 Lr6c2a]tRtRtoRtRtRtRtVtR#) DocFileCasei cjRPVPPPR44#)rr)rrrJrrs&r4r DocFileCase.id s&xx **00566r6c.VPP#r,)rryrs&r4r9DocFileCase.__repr__ s}}%%%r6cnRVPP: RVPP: RV: 2#)rrz ", line 0 )rrJry)r:rs&&r4rDocFileCase.format_failure s(==%%t}}'='=sD r6r<N) r=r>r?r@r r9rrArBrs@r4rr s7&r6rc *Vf/pMVP4pV'dV'g \R4h\YTT;'gR4wrpRV9dWR&\PP V4pVP WsW^4p \V 3/VB#)Nrrr)rrr~rrrr%r) rr{rzrQrYrrrdocrJrs &&&&&&, r4 DocFileTestr s } +, ,to'2274IC j 77  D !D   c$a 8D t 'w ''r6c\4pVPRR4'd\VPR44VR&VFpVP\ V3/VB4K V#)aA 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. r{Trz)rrNrirr)pathskwrrs*, r4rr s^p OE  vv&&)"&&*;<9  k$-"-. Lr6c.p\4PV4Fp\V\4'dyVP VP RR4VP pV'dEVP R4YPR4RRUu.uF pRV,NK up, pKKTVPR4RRUu.uFp\V4NK up, pK V'd!VR,R8XdVP4K(V'd"V^,R8XdVP^4K)RPV4R,#uupiuupi)aExtract 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 Nz # Expected:rz## rr) rr!rZrrrrrrrr)rrpiecerrs& r4rrS s tF&&q) eW % % MM%,,s+ ,::D m,JJt,>2G N 0s A<A<c4\V4p\W1V4R#)z3Debug a single doctest docstring, in argument `src`N)r debug_script)srcpmrQrs&&& r4r!r! s"3'Ge$r6c^RIpV'dVP4pM/pV'd\WV4R#VP !RR7PRV,W"4R# \\P !4^,4TP !RR7pTP4TPR\P !4^,4R#;i)z7Debug a test script. `src` is the script, as a string.NT)rzexec(%r)) rrrrr_rrr interactionr")rrrQrps&&& r4rr s    3 U # "":#3UB  3 #,,.# $&A GGI MM$ q 1 2s A##A6Cc^\V4p\W4p\W2VP4R#)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)rir rrd)rgrJrrs&&& r4r"r" s&v &F&Gfoo.r6c6a]tRtRtoRtRtRtRtRtVt R#) _TestClassi z 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 WnR#)zdval -> _TestClass object with associated value val. >>> t = _TestClass(123) >>> print(t.get()) 123 Nr)r:rs&&r4r_TestClass.__init__ s r6c 6VP^,VnV#)zWsquare() -> square TestClass's associated value >>> _TestClass(13).square().get() 169 rrs&r4square_TestClass.square s88q= r6c VP#)z^get() -> return TestClass's associated value. >>> x = _TestClass(-42) >>> print(x.get()) -42 rrs&r4rN_TestClass.get s xxr6rN) r=r>r?r@rrrrNrArBrs@r4rr s r6rrz Example of a string object, searched as-is. >>> x = 1; y = 2 >>> x + y, x * y (3, 2) zbool-int equivalencea 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 linesz Blank lines can be marked with : >>> print('foo\n\nbar\n') foo bar ellipsisz 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] zwhitespace normalizationa 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] c :^RIpVPRRR7pVPRRRRR R 7VPR R R \P 4.RR7VPRRRRR7VPRRRR7VP 4pVP pVPp^pVPFpV\V,,pK VP'dV\,pVFpVPR4'dq\PPV4wr\PP!^V4\#VRR4p \P^\%WVR7wrM\'VRWER7wrV 'gK^# ^#)rNzdoctest runnerT) descriptioncolorrz --verbose store_trueFz'print very verbose output for all tests)actiondefaulthelpz-oz--optionrzqspecify a doctest option flag to apply to the test run; may be specified more than once to apply multiple options)rchoicesrrz-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))rrrr9z file containing the tests to run)nargsrz.pyrw)r{rXr)argparseArgumentParser add_argumentrGkeys parse_argsrrXr= fail_fastrrrrrr_insertr\rr) rrYr testfilesrXrr=rydirnamer rrs r4_testr; s  $ $1A $ NF k,FH j 3 8 8 :BEG  mLFH c?A    D IllGG++&v.. ~~~9   U # #!# h 7 G HHOOAw '8CR=)A !!'JKHa"8U-4KKH 8 r6r)r)) NNNNTrNFF)FNoNameNrr)FNr)Zr __docformat____all__rLrUrrXrbrrrr_rrior#r$ collectionsr%rr&r' __unittestr)rGrrrrrrrr r r r r rrrMrrUrirmr~rrrrrrrrrsrrrrrr+r Exceptionrrrryrrrrrrrr TestSuiterrrrrrr r!rr"rrrr=exitr<r6r4rs%N& + + +  +   +   +  + + + + + +  + + + $%+ &'+ *++ ./+ 23+ 45+ 67+ 89+ :;+ >?+ @A+ BC+ FG+ HI+ JK+ NO+ PQ+ RS+ T U+ Z 2". &*],>?&LO--EF+,CD*+AB z *6"-.GH*)*()  , ,#>2 ">2 ">2 /0KL  ,   -- !& >2D"$/     /b4"%CGG"%J ,\B$B$HGDGDZd;d;VMMf o/o/dP5P5dY&)&e1-e1\ fLR(,$dU=?yLx46!Hb0(##b0Hk" H&& >@ + '+D=?(4CRP$d % C( /**X *  #%(   ')Q0 f* Z zHHUWr6