3j;SSKrSSKrSSKrSSKrSSKrSSKJrJr SSKJ r SSK r Sr SSK Jr SrSrS rS rS rS r"S S\5r"SS\5r\"S5\\\\\4r\\4- r\"SS\55r!Sr"Sr#Sr$S"Sjr%S"Sjr&SS\!RN4Sjr(Sr)Sr*Sr+Sr,Sr-Sr.S"S jr/S!r0g!\ a Sr Nf=f!\a \\ 4- rNlf=f)#N)Enumunique)wrapsTF)Sequencez1.7.2z%valuesz %file_pathz %yaml_loaderz%unpackz %index_lenc.^\rSrSrU4SjrSrSrU=r$)_NamedDataList(c8>[[U] U5 XlgN)superr__init__name)selfrargs __class__s =/home/wildlama/miniconda3/lib/python3.13/site-packages/ddt.pyr _NamedDataList.__init__)s nd,T2 c,[UR5$r strrrs r__str___NamedDataList.__str__-499~rr__name__ __module__ __qualname____firstlineno__r r__static_attributes__ __classcell__rs@rrr(srrc.^\rSrSrU4SjrSrSrU=r$)_NamedDataDict1c >SUR5;a [S5eURS5Ul[[ U]U5 g)Nrz3@named_data expects a dictionary with a 'name' key.)keysKeyErrorpoprr r&r )rkwargsrs rr _NamedDataDict.__init__2s<  &PQ QJJv&  nd,V4rc,[UR5$r rrs rr_NamedDataDict.__str__8rrrrr$s@rr&r&1s5 rr&c \rSrSrSrSrSrSrg)TestNameFormatCao An enum to configure how ``mk_test_name()`` to compose a test name. Given the following example: .. code-block:: python @data("a", "b") def testSomething(self, value): ... if using just ``@ddt`` or together with ``DEFAULT``: * ``testSomething_1_a`` * ``testSomething_2_b`` if using ``INDEX_ONLY``: * ``testSomething_1`` * ``testSomething_2`` rN)rrr r!__doc__DEFAULT INDEX_ONLYr"r4rrr1r1Cs*GJrr1c[U[5(ag[U[[45(a[ [ [ U55$g)NTF) isinstance trivial_typeslisttupleallmap is_trivial)values rr?r?^s8%'' ED%= ) )3z5)** rc([U[S5 U$)z* Method decorator to add unpack feature. T)setattr UNPACK_ATTR)funcs runpackrEfs  D+t$ Krc[U5$)zs Method decorator to add to your test methods. Should be added to methods of instances of ``unittest.TestCase``. )idata)valuess rdatarIos =rcn^^Tc([T5m[[[T555mUU4SjnU$)a Method decorator to add to your test methods. Should be added to methods of instances of ``unittest.TestCase``. :param iterable: iterable of the values to provide to the test function. :param index_len: an optional integer specifying the width to zero-pad the test identifier indices to. If not provided, this will add the fewest zeros necessary to make all identifiers the same length. cL>[U[T5 [U[T5 U$r )rB DATA_ATTR INDEX_LEN)rD index_leniterables rwrapperidata..wrappers i*i+ r)r<lenr)rOrNrPs`` rrGrGys3?CM*+  Nrc^^UU4SjnU$)a Method decorator to add to your test methods. Should be added to methods of instances of ``unittest.TestCase``. ``value`` should be a path relative to the directory of the file containing the decorated ``unittest.TestCase``. The file should contain JSON encoded data, that can either be a list or a dict. In case of a list, each value in the list will correspond to one test case, and the value will be concatenated to the test method name. In case of a dict, keys will be used as suffixes to the name of the test case, and values will be fed as test data. ``yaml_loader`` can be used to customize yaml deserialization. The default is ``None``, which results in using the ``yaml.safe_load`` method. cZ>[U[T5 T(a[U[T5 U$r )rB FILE_ATTRYAML_LOADER_ATTR)rDr@ yaml_loaders rrPfile_data..wrappers$i'  D*K 8 rr4)r@rWrPs`` r file_datarYs, NrcDSRUS-U5nU[RLd[U5(dSRX5$[ U5nSRXU5n[R"SSU5$![ a UR SS5nNHf=f) a Generate a new name for a test case. It will take the original test name and append an ordinal index and a string representation of the value, and convert the result into a valid python identifier by replacing extraneous characters with ``_``. We avoid doing str(value) if dealing with non-trivial values. The problem is possible different names with different runs, e.g. different order of dictionary keys (see PYTHONHASHSEED) or dealing with mock objects. Trivial scalar values are passed as is. A "trivial" value is a plain scalar, or a tuple or list consisting only of trivial values. The test name format is controlled by enum ``TestNameFormat`` as well. See the enum documentation for further details. z{0:0{1}}r3z{0}_{1}asciibackslashreplacez {0}_{1}_{2}z \W|^(?=\d)_) formatr1r7r?rUnicodeEncodeErrorencoderesub)rr@indexrNname_fmt test_names r mk_test_namergs,   eai 3E>,,,Ju4E4E,,:E $$T%8I 66-i 00 : W&89:s BBBcd^^^[R"T5(a[T5UUU4Sj5nO[T5UUU4Sj5nXlTUlUbX%lU$TR (a$TR R "T0TD6UlU$U$![[4a U$f=f)zG This internal method decorator feeds the test data item to the test. c8># T"U/TQ70TD6IShvN $N7fr r4rrrDr,s rrPfeed_data..wrappers!d4T4V44 44s c>T"U/TQ70TD6$r r4rjs rrPrks.t.v. .r) inspectiscoroutinefunctionrr __wrapped__r5r_ IndexErrorr*)rDnew_nametest_data_docstringrr,rPs` `` r feed_datarss ""4(( t 5  5 t /  / G&- N << "&,,"5"5t"Fv"F N7N )   N  s6!BB/.B/c 8[X[X1U/UQ70UD65 g)zn Add a test case to this class. The test will be based on an existing function but will give it a new name. N)rBrs)clsrftest_docstringrDrr,s radd_testrws) CId~ rch^[RR[R"U55n[RR [RR U5T5nU4Sjn[RRU5(d#[US5nSn[XUU"S5S5 gURS5n U (a/[(d$[US5nSn[UUUU"S5S5 g[R"USS 5n U (aQ[U[5(a%[!U[5n ["R$"XS 9n O-["R&"U 5n O[(R$"U 5n SSS5 [+XUW 5 g!,(df  N=f) z5 Process the parameter in the `file_data` decorator. c>^UU4SjnU$)Nc >[TT-5er ) ValueError)r file_attrmessages rrD:process_file_data..create_error_func..funcsWy01 1rr4)r}rDr|s` rcreate_error_func,process_file_data..create_error_funcs  2 rerrorzError!z%s does not existN)z.ymlz.yamlz(%s is a YAML file, please install PyYAMLrzutf-8)Loader)ospathabspathrm getsourcefilejoindirnameexistsrgrwendswith _have_yamlcodecsopenhasattrrVgetattryamlload safe_loadjson_add_tests_from_data) rurrDr|cls_pathdata_file_pathrrfrv _is_yaml_filefrWrIs ` rprocess_file_datarsJwww44S9:HWW\\"''//(";YGN 77>>. ) ) w/ %"#67 ?"++,=>MZZ w/ %    H I     ^S' 2a t-..%d,<= yy7~~a(99Q Add tests from data loaded from the data file into the class N)rRr enumerater9dictrgr;rw) rurrDrIrNielemkeyr@rfs rrr/sCD N#IT? dD ! !Dz$T=I d # #E$T!?I eT " " S)Y > > S)Ye <#rc$[US5(+$)zNFinds out if the obj is a "primitive". It is somewhat hacky but it works. __dict__)r)objs r _is_primitiverAssJ' ''rc^[U5(dUR(a UR$g)zReturns a docstring based on the following resolution strategy: 1. Passed value is not a "primitive" and has a docstring, then use it. 2. In all other cases return None, i.e the test name is used. N)rr5)rDr@s r_get_test_data_docstringrGs"   EMM}}rc ^URS[R5mU4Sjn[R"U5(aU"U5$U$)a Class decorator for subclasses of ``unittest.TestCase``. Apply this decorator to the test case class, and then decorate test methods with ``@data``. For each method decorated with ``@data``, this will effectively create as many methods as data items are passed as parameters to ``@data``. The names of the test methods follow the pattern ``original_test_name_{ordinal}_{data}``. ``ordinal`` is the position of the data argument, starting with 1. For data we use a string representation of the data value converted into a valid python identifier. If ``data.__name__`` exists, we use that instead. For each method decorated with ``@file_data('test_data.json')``, the decorator will try to load the test_data.json file located relative to the python file containing the method that is decorated. It will, for each ``test_name`` key create as many methods in the list of values from the ``data`` key. Decorating with the keyword argument ``testNameFormat`` can control the format of the generated test names. For example: - ``@ddt(testNameFormat=TestNameFormat.DEFAULT)`` will be index and values. - ``@ddt(testNameFormat=TestNameFormat.INDEX_ONLY)`` will be index only. - ``@ddt`` is the same as DEFAULT. testNameFormatc >[URR55GH,up[U[5(a[ U[ 5n[[ U[55HupE[U[ USU5UUT 5n[X%5n[U[5(aL[U[5(d[U[5(a[UUUU/UQ76 Mz[UUUU40UD6 M[XXrU5 M [X5 M[U[5(dGM[ U[5n[!XX(5 [X5 GM/ U$)Nr)r;ritemsrrLrrMrrgrrCr9r<rwdelattrrUr) rurrDrNrvrfrrr| fmt_test_names rrPddt..wrapperus4s||1134JDtY''#D)4 %gdI&>?DA ,:q1!% !I+C4*K't[11%a//:a3F3F$ # ) 3 $  "# % # ) 3 $  #$ !1DAN9@:"y))#D)4 !#T="I5J r)getr1r6rmisclass)argr,rPrs @rddtrRsBBJJ/1G1GHM&T#??3//73<[T6"[U55 U$r )rIrE)rDrHs rrPnamed_data..wrappers f fTl# rr4) r9rr TypeErrorr_typer&rr5append) named_values named_valuer@rPrHs @r named_datars@F# +$'788[bbcghsctu 2rs; J$   !  TTdT3~~N j^#M T40<%&^=S=S1DB .0b=$( M=`3a JZcWMs#B7!C7CC CC