KhuF SrSSKrSSKrSSKrSSKrSSKrSSKrSSKrSSKrSSK J r J r SSK r SSK r SSKJrJr SSKJr SSKJr SSKrSSKrSSKrSSKrSSKrSSKrSSKJrJrJ r J!r!J"r"J#r#J$r$J%r% SSKJ&r&J'r'J(r( SSK)rSS K*J+r+ SS K,J-r- SS K.J/r/ /S Qr0"S S\15r2\2r3Sr4\Rj"\Rl5Rnr8\RrRuS5r;Sr<\RzS:a!\;R|R~RrAOISSKBrBSSKCrC\BR"\;RS5=(d SSS9r>\>R~RrA\A(d\;RS5\8:waSr<\R"5S;rJ\RRS:HrM\N"\S5rO\P"\SS5SL=(a \O(+rQ\RRRrUSrV\R"S5=(d SrXS\X;aSrV\Y"\R"S55rZ\R"\R<5RS:Hr]SkS jr^\RS!:Xa SlS"jr_SmS#jr`O0\RSS$S%:XaS&\R"5S'34S(jr`OS)r`\RSS$S%:XaS&\R"5S'3/4S*jrbO/4S+jrbSnS-jrcSoSS..S/jjrdS0reSpS1jrfSpS2jrgSqSS,S3.S4jjrh\+"S5S6/S7S8/S9S:9SoSS..S;jj5ri\+"S5S6/S7S8/S9S:9SrS<j5rjSoSS..S=jjrkS>rlS?rmSsS@jrn/4SAjroSSKprp"SBSC\pR5rr\r"SD5rsSErtSFruStSGjrvSuSHjrwSIrxSvSS..SJjjrySwSKjrzSuSLjr{StSMjr|SNr}SOr~\ RStSPj5rSQr\ RStSRj5rSSr\STSU4SVjr"SWSX\15r\ RSY5r\ RSZ5r"S[S\\GR5r"S]S^5r\ RStS_j5rS`rSarSbrScrSdrSerSfrSgr\"5rShrSxSijrSySjjrg!\Fa SrAGNf=f!\RrRa S=rrXMs)>)>)F)FrO) object_hookF)wasm32wasm64pypypyston_version_info getrefcount HOST_GNU_TYPEmuslPy_GIL_DISABLEDc`SnU(dU"5n[U5eg![a UnNf=f)a1 Assert that works in release mode. Accepts callable msg to allow deferring evaluation until failure. The Python built-in ``assert`` does not work when executing code in optimized mode (the ``-O`` flag) - no byte-code is generated for it. For documentation on usage, refer to the Python documentation. TN) TypeErrorAssertionError)valmsg__tracebackhide__smsgs rPr(r(nsA  5DT""  D s  --ntcSSKnUc URnURXPUSX145nUR5nUR X5n UR U5 UR X5upU URU 5 URU5 $!URU 5 f=f!URU5 f=f)Nr) win32pdh PDH_FMT_LONGMakeCounterPath OpenQuery AddCounterCollectQueryDataGetFormattedCounterValue RemoveCounter CloseQuery) objectcounterinstanceinumformatmachinermpathhqhctypergs rPGetPerformanceAttributesrs  >**F''(D)-)89    ! $$$R.B +))"-$==bI &&r*    #&&r*    #s#B* %B1B*B''B**B=c<SSKn[SSXURS5$)NrProcessz Virtual Bytes)rmrrn) processNamerxrms rPr"r"s&' ?(3(0(=(=tE ErOlinuxz/proc/z/statc[U5nUR5RS5nSSS5 [WS5$!,(df  N=f![a gf=f)z= Return virtual memory size in bytes of the running python.  N)openreadlinesplitint Exception)_proc_pid_statfls rPr"r"sV  n%JJL&&s+&qu: &%   s' A AA A A A! A!c[e)z; Return memory usage of running python. [Not implemented] )NotImplementedErrorrGrOrPr"r"s "!rOc`SSKnU(dURUR55 [U5nUR5R S5nSSS5 [ WS5$!,(df  N=f![ a% [ SUR5US- -5s$f=f) Return number of jiffies elapsed. Return number of jiffies (1/100ths of a second) that this process has been scheduled in user mode. See man 5 proc. rNrrSd)timeappendrrrrr)r _load_timerrrs rPr!r!s    diik * <n%JJL&&s+&qu: &% <sdiikJqM9:; ; A-A>- A;7A>>,B-,B-cSSKnU(dURUR55 [SUR5US- -5$)rrNr)rrr)rrs rPr!r!s=    diik *3$))+ 1 5677rOACTUALDESIREDcSU-/n[U5nU(aNURS5S:Xa([U5S[U5- :a USS-U-/nOURU5 U(a[ U5Hupx[ U[ 5(a[[US9n O[n U "U5n U RS5S :a'SRU R5SS 5n U S - n URSXGS U 35 M SRU5$![a&n S[U5RSU S 3n Sn A NSn A ff=f) N Orr) precisionz[repr failed for : ]rRz...: )strfindlenr enumerate isinstancerrr reprrrrIcountjoin splitlines) arrayserr_msgheaderr&namesrrhiar_funcrexcs rPrrs4 &=/C'lG <<  #G rCK7G(Gq6C<')*C JJw f%DA!W%% yA E1Iwwt}q IIallnRa01U  JJ58*Bqc* +& 99S>  E(a)9)9(:#cU!D Es)D E %EE strictc 6Sn[U[5(a[U[5(d[[[ U555e[ [ U5[ U5X#5 UR5H7upgX`;a[[U55e[ XXSU<SU3U5 M9 g[U[[45(ao[U[[45(aT[ [ U5[ U5X#5 [[ U55Hn[ XXSU<SU3U5 M gSSK J nJ n Jn SSKJn Jn Jn [X5(d[X5(a ['XX#US 9$[)X/X#S 9nU "U5=(d U "U5nU(a]U "U5(aU "U5nU "U5nOUnSnU "U5(aU "U5nU "U5nOUnSn[ UU5 [ UU5 U "U5U "U5:wa [U5e[/U5n[/U5n[0R2"U5R4R[0R2"U5R4R:HnU(aU(aU(ag[U5e[9U5n[9U5nU(aU(ag[0R2"U5n[0R2"U5nUR4R:S ;dUR4R:S ;a [7S 5eUS:Xa#US:XaU "U5U "U5:Xd [U5eX:Xd [U5eg![*[,4a S nGNf=f![a [U5ef=f![,[*[64a GNf=f![,[*[64a Nwf=f![<[>4a$nSUR@S;a [U5eeSnAff=f)a$ Raises an AssertionError if two objects are not equal. Given two objects (scalars, lists, tuples, dictionaries or numpy arrays), check that all elements of these objects are equal. An exception is raised at the first conflicting values. This function handles NaN comparisons as if NaN was a "normal" number. That is, AssertionError is not raised if both objects have NaNs in the same positions. This is in contrast to the IEEE standard on NaNs, which says that NaN compared to anything must return False. Parameters ---------- actual : array_like The object to check. desired : array_like The expected object. err_msg : str, optional The error message to be printed in case of failure. verbose : bool, optional If True, the conflicting values are appended to the error message. strict : bool, optional If True and either of the `actual` and `desired` arguments is an array, raise an ``AssertionError`` when either the shape or the data type of the arguments does not match. If neither argument is an array, this parameter has no effect. .. versionadded:: 2.0.0 Raises ------ AssertionError If actual and desired are not equal. See Also -------- assert_allclose assert_array_almost_equal_nulp, assert_array_max_ulp, Notes ----- By default, when one of `actual` and `desired` is a scalar and the other is an array, the function checks that each element of the array is equal to the scalar. This behaviour can be disabled by setting ``strict==True``. Examples -------- >>> np.testing.assert_equal([4, 5], [4, 6]) Traceback (most recent call last): ... AssertionError: Items are not equal: item=1 ACTUAL: 5 DESIRED: 6 The following comparison does not raise an exception. There are NaNs in the inputs, but they are in the same positions. >>> np.testing.assert_equal(np.array([1.0, 2.0, np.nan]), [1, 2, np.nan]) As mentioned in the Notes section, `assert_equal` has special handling for scalars when one of the arguments is an array. Here, the test checks that each value in `x` is 3: >>> x = np.full((2, 5), fill_value=3) >>> np.testing.assert_equal(x, 3) Use `strict` to raise an AssertionError when comparing a scalar with an array of a different shape: >>> np.testing.assert_equal(x, 3, strict=True) Traceback (most recent call last): ... AssertionError: Arrays are not equal (shapes (2, 5), () mismatch) ACTUAL: array([[3, 3, 3, 3, 3], [3, 3, 3, 3, 3]]) DESIRED: array(3) The `strict` parameter also ensures that the array data types match: >>> x = np.array([2, 2, 2]) >>> y = np.array([2., 2., 2.], dtype=np.float32) >>> np.testing.assert_equal(x, y, strict=True) Traceback (most recent call last): ... AssertionError: Arrays are not equal (dtypes int64, float32 mismatch) ACTUAL: array([2, 2, 2]) DESIRED: array([2., 2., 2.], dtype=float32) Tzkey=rNzitem=r)risscalarsignbit iscomplexobjrealimagrr&FMmz0cannot compare to a scalar with a different typezelementwise == comparison)!rdictrfrrrritemslisttuplerange numpy._corerrrrQrrrrr ValueErrorrernpasarraydtyperrcharDeprecationWarning FutureWarningargs)actualdesiredrr&rrikrrrrrrrrh usecomplexactualractualidesiredrdesirediisdesnatisactnat dtypes_matchisdesnanisactnan array_actual array_desiredes rPrrsF'4  &$'' d6l!34 4S[#g,AMMODA$T!W-- GJ$qe2gY0G  "$ 'D%=))j$.O.OS[#g,As7|$A GJ%uBwi0H  "% 66..&""j&B&B!&7)/1 1 )7 DC !&)B\'-B    6lG6lGGG  G}HG}HHH & ( + ( + HV,,S!! >= 7+1166 6*00556 $S))  >=  zz&)  7+    # #t +##((D0 &'>? ? a>> np.testing.print_assert_equal('Test XYZ of func xyz', [0, 1], [0, 1]) >>> np.testing.print_assert_equal('Test XYZ of func xyz', [0, 1], [0, 2]) Traceback (most recent call last): ... AssertionError: Test XYZ of func xyz failed ACTUAL: [0, 1] DESIRED: [0, 2] TrNz failed ACTUAL: z DESIRED: )pprintrwriterfgetvalue) test_stringrrrirrhs rPr#r#sm8  j + '( f" -  g#S\\^,, rOc^^^^^SnSSKJn SSKJnJnJn U"T5=(d U"T5n UUUUU4Sjn U (aYU"T5(aU"T5n U "T5n OTn Sn U"T5(aU"T5nU "T5nOTnSn[XTS9 [XTS9 [TU[[45(d[TU[[45(a[TTTT5$[T5(a[T5(di[T5(d[T5(a2[T5(a[T5(d[U "55egTT:Xd[U "55eg[#TT- 5[$R&"S S T*--5:a[U "55eg![ a Sn GNf=f![a [U "55ef=f![[ 4a Nf=f) aj Raises an AssertionError if two items are not equal up to desired precision. .. note:: It is recommended to use one of `assert_allclose`, `assert_array_almost_equal_nulp` or `assert_array_max_ulp` instead of this function for more consistent floating point comparisons. The test verifies that the elements of `actual` and `desired` satisfy:: abs(desired-actual) < float64(1.5 * 10**(-decimal)) That is a looser test than originally documented, but agrees with what the actual implementation in `assert_array_almost_equal` did up to rounding vagaries. An exception is raised at conflicting values. For ndarrays this delegates to assert_array_almost_equal Parameters ---------- actual : array_like The object to check. desired : array_like The expected object. decimal : int, optional Desired precision, default is 7. err_msg : str, optional The error message to be printed in case of failure. verbose : bool, optional If True, the conflicting values are appended to the error message. Raises ------ AssertionError If actual and desired are not equal up to specified precision. See Also -------- assert_allclose: Compare two array_like objects for equality with desired relative and/or absolute precision. assert_array_almost_equal_nulp, assert_array_max_ulp, assert_equal Examples -------- >>> from numpy.testing import assert_almost_equal >>> assert_almost_equal(2.3333333333333, 2.33333334) >>> assert_almost_equal(2.3333333333333, 2.33333334, decimal=10) Traceback (most recent call last): ... AssertionError: Arrays are not almost equal to 10 decimals ACTUAL: 2.3333333333333 DESIRED: 2.33333334 >>> assert_almost_equal(np.array([1.0,2.3333333333333]), ... np.array([1.0,2.33333334]), decimal=9) Traceback (most recent call last): ... AssertionError: Arrays are not almost equal to 9 decimals Mismatched elements: 1 / 2 (50%) Max absolute difference among violations: 6.66669964e-09 Max relative difference among violations: 2.85715698e-09 ACTUAL: array([1. , 2.333333333]) DESIRED: array([1. , 2.33333334]) Tr)rrFc*>ST-n[TT/TTUS9$)N*Arrays are not almost equal to %d decimals)r&r)r)rrdecimalrrr&s rP_build_err_msg+assert_almost_equal.._build_err_msgIs(>Hfg.$*, ,rO)rN?$@)rrrQrrrrrrfrrrrrrrreabsrfloat64)rrrrr&rirrrrrrrrrrs````` rPrrsJ#.. !&)B\'-B ,,    6lG6lGGG  G}HG}HHH 3 7 C 7 C&7E4011'GUD#9::('7KK  !!hv&6&6W~~vg5==()9::,9 &(()9:: '7 7V  31A+A BB^-..CY  0 3 !12 2 3$  +   s6F)F<!A1GG) F98F9<GG-,G-c hSnSSKn[[X45upX:XagUR"SS9 SUR"U5UR"U5--nUR "SUR "UR"U555nSSS5 UW- nUW- n [X/US U-US 9n [U5(a[U5(d^[U5(d[U5(a-[U5(a[U5(d [U 5egX:Xd [U 5egUR"X- 5UR "S US - *5:a [U 5eg!,(df  N=f![a SnNf=f![a Sn Nf=f![[4a Nf=f) a Raises an AssertionError if two items are not equal up to significant digits. .. note:: It is recommended to use one of `assert_allclose`, `assert_array_almost_equal_nulp` or `assert_array_max_ulp` instead of this function for more consistent floating point comparisons. Given two numbers, check that they are approximately equal. Approximately equal is defined as the number of significant digits that agree. Parameters ---------- actual : scalar The object to check. desired : scalar The expected object. significant : int, optional Desired precision, default is 7. err_msg : str, optional The error message to be printed in case of failure. verbose : bool, optional If True, the conflicting values are appended to the error message. Raises ------ AssertionError If actual and desired are not equal up to specified precision. See Also -------- assert_allclose: Compare two array_like objects for equality with desired relative and/or absolute precision. assert_array_almost_equal_nulp, assert_array_max_ulp, assert_equal Examples -------- >>> np.testing.assert_approx_equal(0.12345677777777e-20, 0.1234567e-20) >>> np.testing.assert_approx_equal(0.12345670e-20, 0.12345671e-20, ... significant=8) >>> np.testing.assert_approx_equal(0.12345670e-20, 0.12345672e-20, ... significant=8) Traceback (most recent call last): ... AssertionError: Items are not equal to 8 significant digits: ACTUAL: 1.234567e-21 DESIRED: 1.2345672e-21 the evaluated condition that raises the exception is >>> abs(0.12345670e-20/1e-21 - 0.12345672e-20/1e-21) >= 10**-(8-1) True TrNignore)invalidg? gz-Items are not equal to %d significant digits:)rr&r)rQmapfloaterrstaterpowerfloorlog10ZeroDivisionErrorrrrrfrer) rr significantrr&rirscale sc_desired sc_actualrhs rPrrvsvEF#45V X &rvvg78RXXbhhuo67 'u_ UN   7>L C  !!hv&6&6W~~vg5==(--,9 ((-- '7 vvj$%#q7I)JJS!!K; ' &    $ * +   sIAE)E:F 1A,FF) E7: F F  FFF10F1)rrc   ^^^^^ ^2Sn SSKJn Jn Jm2JnJnJnJn [R"U5n[R"U5nXnnSnSnSnU S4UUU UU4SjjnU (a:URUR:H=(a URUR:HnOEURS :H=(d URS :H=(d URUR:HnU(drURUR:waS URS URS 3nOS URS URS 3n[X/TU-TTT TS9n[U5e[R"S5nU"U5(aCU"U5(a6U(aU"XU SS9nU(aUU"XU24SjSS9-nUU"XU24SjSS9-nGO,U"U5(aOU"U5(aBU(a:URRURR:Xa U"X[ SS9nOU"U5(aU"U5(aURnU(aUUR:Xa[#US5(a[%UR&[(5=(a [R"UR&5nSn[UR&5 U(dU(aU"XXRR&S9nUR,S:aUU)UU)p!UR.S:XagOU(agU"X5n[R0"U5n [%U[5(aUn[3U/5n!O UR55n!U!R 5nUS:wGa_U!R.U!R7[8S9- n"UR,S:wa UR.O U!R.n#SU"-U#- n$SR;U"U#U$5/n%U"SS9 [<R>"[*5 [AX- 5n&[RB"UR[RD5(a#[AX!- 5n'[RF"U&U'U&S9 U&U n(U"U(5n)[IU&SU5U:XaU%RKS[MU)5-5 OU%RKSU "U)5-5 [R"US:g5n*[RN"U U*5n+U"U+)5(a [3T25n,O?U&U+n-[RP"UU&R5n.U.U+n/U"U-[AU/5- 5n,[IU&SU5U:XaU%RKS [MU,5-5 OU%RKS U "U,5-5 SSS5 SSS5 [MT5mTS!S!RSU%5-- m[UU/TTTT TS9n[U5eg![*a SnGN6f=f!,(df  Ng=f!,(df  Np=f![Ta7 SSK+n0U0RY5n1S"U1S#T3m[X/TTTT TS9n[UU5ef=f)$NTr) array2stringrinfrallmaxobject_c4URRS;$)Nz?bhilqpBHILQPefdgFDGrrxs rPisnumber&assert_array_compare..isnumbersww||555rOc4URRS;$)Nrrrs rPistime$assert_array_compare..istimesww||t##rOc4URRS:H$)NTrrs rP isvstring'assert_array_compare..isvstringsww||s""rOnanc >SnU"U5nU"U5n[R"XV:H5R5S:wa [X/TSU--T T T T S9n[ U5e[ U[5(dUR S:Xa[R"U5$[ U[5(dUR S:Xa[R"U5$U$)zsHandling nan/inf. Combine results of running func on x and y, checking that they are True at the same locations. Tz %s location mismatch:r&rrrr)rboolrrrfrndim) ryfunchasvalrix_idy_idrhrrrrr&s rPfunc_assert_same_pos2assert_array_compare..func_assert_same_poss!AwAw 774< $ $ &$ .3$+F# %C !% % dD ! !TYY!^774= d # #tyyA~774= KrOrGz (shapes z, z mismatch)z (dtypes rF)rrc>UT7:H$NrGxyrs rPrX&assert_array_compare..0 sd rOz+infc>UT*:H$rrGrs rPrXr!3r"rOz-infNaT na_objectrrrz&Mismatched elements: {} / {} ({:.3g}%)r)routrz*Max absolute difference among violations: z*Max relative difference among violations: rzerror during assertion: z )-rrrrrrrrr asanyarrayshaperrrfrrrhasattrrr%rrersize logical_notrravelsumr rz contextlibsuppressr issubdtypeunsignedintegerminimumgetattrrr logical_and broadcast_torr traceback format_exc)3 comparisonrrrr&rr equal_nan equal_infrrrirrrrrroxoyrr rrcondreasonrhflaggeddtis_nan bool_errorsrginvalidsreduced n_mismatch n_elementspercent_mismatchremarkserrorerror2 reduced_error max_abs_errornonzerononzero_and_invalid max_rel_errornonzero_invalid_error broadcasted_ynonzero_invalid_yr8efmtrs3 ```` ` @rPr8r8s/// aA aAB6$#).e%%NJ 77agg%>#& c4 DSElGiikG;;=D 4<  $ (??J)0): J"Z/*< 8?? ,<>?Gh'((3JE}}QWWb.@.@AA!$QU 5&e<$)(OM$' $6Mugw77BH!-012 H*=9:;!gga1foG*,..7*K'//00(-c 056I0J-(*5;;(G ,9:M,N)(+,A.12C.D-E)F ugw77BH!-012 H*=9:;K4(T'lG tdii00 0GR'(/&+*35C!% %q =!$"#K$P43('b ##%.tfDAQFGWV"'9>osr"IX&5W1 AX&X&(CX&;XF X#X+AX&1 X=X&XX& X X X#X&&AY'rrrrz2.0.0) dep_versionc @Sn[[RXUUSUS9 g)a` Raises an AssertionError if two array_like objects are not equal. Given two array_like objects, check that the shape is equal and all elements of these objects are equal (but see the Notes for the special handling of a scalar). An exception is raised at shape mismatch or conflicting values. In contrast to the standard usage in numpy, NaNs are compared like numbers, no assertion is raised if both objects have NaNs in the same positions. The usual caution for verifying equality with floating point numbers is advised. .. note:: When either `actual` or `desired` is already an instance of `numpy.ndarray` and `desired` is not a ``dict``, the behavior of ``assert_equal(actual, desired)`` is identical to the behavior of this function. Otherwise, this function performs `np.asanyarray` on the inputs before comparison, whereas `assert_equal` defines special comparison rules for common Python types. For example, only `assert_equal` can be used to compare nested Python lists. In new code, consider using only `assert_equal`, explicitly converting either `actual` or `desired` to arrays if the behavior of `assert_array_equal` is desired. Parameters ---------- actual : array_like The actual object to check. desired : array_like The desired, expected object. err_msg : str, optional The error message to be printed in case of failure. verbose : bool, optional If True, the conflicting values are appended to the error message. strict : bool, optional If True, raise an AssertionError when either the shape or the data type of the array_like objects does not match. The special handling for scalars mentioned in the Notes section is disabled. .. versionadded:: 1.24.0 Raises ------ AssertionError If actual and desired objects are not equal. See Also -------- assert_allclose: Compare two array_like objects for equality with desired relative and/or absolute precision. assert_array_almost_equal_nulp, assert_array_max_ulp, assert_equal Notes ----- When one of `actual` and `desired` is a scalar and the other is array_like, the function checks that each element of the array_like object is equal to the scalar. This behaviour can be disabled with the `strict` parameter. Examples -------- The first assert does not raise an exception: >>> np.testing.assert_array_equal([1.0,2.33333,np.nan], ... [np.exp(0),2.33333, np.nan]) Assert fails with numerical imprecision with floats: >>> np.testing.assert_array_equal([1.0,np.pi,np.nan], ... [1, np.sqrt(np.pi)**2, np.nan]) Traceback (most recent call last): ... AssertionError: Arrays are not equal Mismatched elements: 1 / 3 (33.3%) Max absolute difference among violations: 4.4408921e-16 Max relative difference among violations: 1.41357986e-16 ACTUAL: array([1. , 3.141593, nan]) DESIRED: array([1. , 3.141593, nan]) Use `assert_allclose` or one of the nulp (number of floating point values) functions for these cases instead: >>> np.testing.assert_allclose([1.0,np.pi,np.nan], ... [1, np.sqrt(np.pi)**2, np.nan], ... rtol=1e-10, atol=0) As mentioned in the Notes section, `assert_array_equal` has special handling for scalars. Here the test checks that each value in `x` is 3: >>> x = np.full((2, 5), fill_value=3) >>> np.testing.assert_array_equal(x, 3) Use `strict` to raise an AssertionError when comparing a scalar with an array: >>> np.testing.assert_array_equal(x, 3, strict=True) Traceback (most recent call last): ... AssertionError: Arrays are not equal (shapes (2, 5), () mismatch) ACTUAL: array([[3, 3, 3, 3, 3], [3, 3, 3, 3, 3]]) DESIRED: array(3) The `strict` parameter also ensures that the array data types match: >>> x = np.array([2, 2, 2]) >>> y = np.array([2., 2., 2.], dtype=np.float32) >>> np.testing.assert_array_equal(x, y, strict=True) Traceback (most recent call last): ... AssertionError: Arrays are not equal (dtypes int64, float32 mismatch) ACTUAL: array([2, 2, 2]) DESIRED: array([2., 2., 2.], dtype=float32) TzArrays are not equal)rr&rrN)r8operator__eq__)rrrr&rris rPrrs&x&7!(1G &(rOc n^^^^ ^ SnSSKJm Jm SSKJm SSKJm UUUU U 4Sjn[X`XUST-TS9 g ) a Raises an AssertionError if two objects are not equal up to desired precision. .. note:: It is recommended to use one of `assert_allclose`, `assert_array_almost_equal_nulp` or `assert_array_max_ulp` instead of this function for more consistent floating point comparisons. The test verifies identical shapes and that the elements of ``actual`` and ``desired`` satisfy:: abs(desired-actual) < 1.5 * 10**(-decimal) That is a looser test than originally documented, but agrees with what the actual implementation did up to rounding vagaries. An exception is raised at shape mismatch or conflicting values. In contrast to the standard usage in numpy, NaNs are compared like numbers, no assertion is raised if both objects have NaNs in the same positions. Parameters ---------- actual : array_like The actual object to check. desired : array_like The desired, expected object. decimal : int, optional Desired precision, default is 6. err_msg : str, optional The error message to be printed in case of failure. verbose : bool, optional If True, the conflicting values are appended to the error message. Raises ------ AssertionError If actual and desired are not equal up to specified precision. See Also -------- assert_allclose: Compare two array_like objects for equality with desired relative and/or absolute precision. assert_array_almost_equal_nulp, assert_array_max_ulp, assert_equal Examples -------- the first assert does not raise an exception >>> np.testing.assert_array_almost_equal([1.0,2.333,np.nan], ... [1.0,2.333,np.nan]) >>> np.testing.assert_array_almost_equal([1.0,2.33333,np.nan], ... [1.0,2.33339,np.nan], decimal=5) Traceback (most recent call last): ... AssertionError: Arrays are not almost equal to 5 decimals Mismatched elements: 1 / 3 (33.3%) Max absolute difference among violations: 6.e-05 Max relative difference among violations: 2.57136612e-05 ACTUAL: array([1. , 2.33333, nan]) DESIRED: array([1. , 2.33339, nan]) >>> np.testing.assert_array_almost_equal([1.0,2.33333,np.nan], ... [1.0,2.33333, 5], decimal=5) Traceback (most recent call last): ... AssertionError: Arrays are not almost equal to 5 decimals nan location mismatch: ACTUAL: array([1. , 2.33333, nan]) DESIRED: array([1. , 2.33333, 5. ]) Tr)number result_type)r2)anyc(>T"[U55(dT"[U55(a`[U5n[U5nX#:HR5(dgURURs=:XaS:XaO OX:H$X)nX)nT "US5n[ R "X5n[X- 5nT"URT 5(dUR[ R5nUSST*--:$![[4a Nf=f)NFrg?rr) rrr,rerrr)rrastyper) rrxinfidyinfidrzrr2npanyr[r\s rPcompare*assert_array_almost_equal..comparezs U1X%a//qq(--// 66QVV(q(6MgJgJ Ar" MM! # J!''6**$A3))))./   sAC>'C> C>>DDr)rr&rrN)rr[r\numpy._core.numerictypesr2numpy._core.fromnumericr]r8) rrrrr&rirdr2rcr[r\s ` @@@@rPrr&s;^/34**4'!(AGK rOc DSn[[RXUUSSUSS9 g)a Raises an AssertionError if two array_like objects are not ordered by less than. Given two array_like objects `x` and `y`, check that the shape is equal and all elements of `x` are strictly less than the corresponding elements of `y` (but see the Notes for the special handling of a scalar). An exception is raised at shape mismatch or values that are not correctly ordered. In contrast to the standard usage in NumPy, no assertion is raised if both objects have NaNs in the same positions. Parameters ---------- x : array_like The smaller object to check. y : array_like The larger object to compare. err_msg : string The error message to be printed in case of failure. verbose : bool If True, the conflicting values are appended to the error message. strict : bool, optional If True, raise an AssertionError when either the shape or the data type of the array_like objects does not match. The special handling for scalars mentioned in the Notes section is disabled. .. versionadded:: 2.0.0 Raises ------ AssertionError If x is not strictly smaller than y, element-wise. See Also -------- assert_array_equal: tests objects for equality assert_array_almost_equal: test objects for equality up to precision Notes ----- When one of `x` and `y` is a scalar and the other is array_like, the function performs the comparison as though the scalar were broadcasted to the shape of the array. This behaviour can be disabled with the `strict` parameter. Examples -------- The following assertion passes because each finite element of `x` is strictly less than the corresponding element of `y`, and the NaNs are in corresponding locations. >>> x = [1.0, 1.0, np.nan] >>> y = [1.1, 2.0, np.nan] >>> np.testing.assert_array_less(x, y) The following assertion fails because the zeroth element of `x` is no longer strictly less than the zeroth element of `y`. >>> y[0] = 1 >>> np.testing.assert_array_less(x, y) Traceback (most recent call last): ... AssertionError: Arrays are not strictly ordered `x < y` Mismatched elements: 1 / 3 (33.3%) Max absolute difference among violations: 0. Max relative difference among violations: 0. x: array([ 1., 1., nan]) y: array([ 1., 2., nan]) Here, `y` is a scalar, so each element of `x` is compared to `y`, and the assertion passes. >>> x = [1.0, 4.0] >>> y = 5.0 >>> np.testing.assert_array_less(x, y) However, with ``strict=True``, the assertion will fail because the shapes do not match. >>> np.testing.assert_array_less(x, y, strict=True) Traceback (most recent call last): ... AssertionError: Arrays are not strictly ordered `x < y` (shapes (2,), () mismatch) x: array([1., 4.]) y: array(5.) With ``strict=True``, the assertion also fails if the dtypes of the two arrays do not match. >>> y = [5, 5] >>> np.testing.assert_array_less(x, y, strict=True) Traceback (most recent call last): ... AssertionError: Arrays are not strictly ordered `x < y` (dtypes float64, int64 mismatch) x: array([1., 4.]) y: array([5, 5]) Tz'Arrays are not strictly ordered `x < y`F)rr)rr&rr<rrN)r8rX__lt__)rrrr&rris rPrrs,T!!( I#( &) +rOc[X5 gr)exec)astrrs rPr%r% s rOcSnSSKn[U[5(d[[ [ U555e[U[5(d[[ [ U555eX:Xag[ UR5RURS5URS555n/nU(GaOURS5nURS5(aM1URS5(aU/nURS5nURS5(a"URU5 URS5nURS5(d[[ U55eURU5 U(aKURS5n U RS5(aURU 5 OURSU 5 USSUSS:XaGM/URU5 GMC[[ U55eU(dgS S RU5R!53n X:wa [U 5eg) aN Test if two strings are equal. If the given strings are equal, `assert_string_equal` does nothing. If they are not equal, an AssertionError is raised, and the diff between the strings is shown. Parameters ---------- actual : str The string to test for equality against the expected string. desired : str The expected string. Examples -------- >>> np.testing.assert_string_equal('abc', 'abc') >>> np.testing.assert_string_equal('abc', 'abcd') Traceback (most recent call last): File "", line 1, in ... AssertionError: Differences in strings: - abc+ abcd? + TrNz z- z? z+ zDifferences in strings: r`)difflibrrrfrrrDifferrdrpop startswithrinsertextendrrstrip) rrrirodiff diff_listd1rd2d3rhs rPrrs6 fc " "T$v,/00 gs # #T$w-011  (():):4)@""4(* +DI  XXa[ ==    ==  A!B}}T"" XXa[==&&$T"X.. HHRLXXa[==&&HHRLKK2&!"vAB   Q  T"X&&  %bggi&8&?&?&A%B CC S!!rOc^ SSKJn SSKnUc%[R"S5nUR Sn[ RR[ RRU55SnU"XP5nUR5RU5nURSS9n/m U(aU 4Sjn OSn UHn URXS 9 M URS:a%U(a[S S R!T 5-5egg) a Run doctests found in the given file. By default `rundocs` raises an AssertionError on failure. Parameters ---------- filename : str The path to the file for which the doctests are run. raise_on_error : bool Whether to raise an AssertionError when a doctest fails. Default is True. Notes ----- The doctests can be run by the user/developer by adding the ``doctests`` argument to the ``test()`` call. For example, to run all tests (including doctests) for ``numpy.lib``: >>> np.lib.test(doctests=True) # doctest: +SKIP r)exec_mod_from_locationNr__file__Frc&>TRU5$r)r)srhs rPrXrundocs..{s  1 rOr'zSome doctests failed: %sr)numpy.distutils.misc_utilr|doctestsys _getframe f_globalsosr|splitextbasename DocTestFinderr DocTestRunnerrunfailuresrfr) filenameraise_on_errorr|rrnamemtestsrunnerr(testrhs @rPr$r$Xs,A MM! ;;z* 77  BGG,,X6 7 :Dt.A  ! ! # ( ( +E  " "5 " 1F C% 4 !~8499S>IJJ .rOcU(aUS$SSKnSnURUSSS9nSUR;nUR U5 US$![UR4a SnN0f=f)z gh-22982 rNlscpuT)capture_outputtextsveF) subprocessrstdoutOSErrorSubprocessErrorr)__cachercmdoutputresults rPr>r>sy qz CDtD&--' NN6 1: Z// 0s A A%$A%c\rSrSrSrSrg)_DummyicgrrG)selfs rPnop _Dummy.nops rOrGN)rIrJrKrLrrNrGrOrPrrs rOrrc2Sn[R"U0UD6$)a assert_raises(exception_class, callable, *args, **kwargs) assert_raises(exception_class) Fail unless an exception of class exception_class is thrown by callable when invoked with arguments args and keyword arguments kwargs. If a different type of exception is thrown, it will not be caught, and the test case will be deemed to have suffered an error, exactly as for an unexpected exception. Alternatively, `assert_raises` can be used as a context manager: >>> from numpy.testing import assert_raises >>> with assert_raises(ZeroDivisionError): ... 1 / 0 is equivalent to >>> def div(x, y): ... return x / y >>> assert_raises(ZeroDivisionError, div, 1, 0) T)_d assertRaises)rkwargsris rPrrs2 ??D +F ++rOc:Sn[R"X/UQ70UD6$)a assert_raises_regex(exception_class, expected_regexp, callable, *args, **kwargs) assert_raises_regex(exception_class, expected_regexp) Fail unless an exception of class exception_class and with message that matches expected_regexp is thrown by callable when invoked with arguments args and keyword arguments kwargs. Alternatively, can be used as a context manager like `assert_raises`. T)rassertRaisesRegex)exception_classexpected_regexprrris rPr*r*s%   R4 R6 RRrOc Uc([R"S[R-5nO[R"U5nURnSSKJn UR5Vs/sHoT"U5(dMUPM nnUHqn[US5(a URnO URnURU5(dMGURS5(aM_[XU"U55 Ms gs snf![a Mf=f)a Apply a decorator to all methods in a class matching a regular expression. The given decorator is applied to all public methods of `cls` that are matched by the regular expression `testmatch` (``testmatch.search(methodname)``). Methods that are private, i.e. start with an underscore, are ignored. Parameters ---------- cls : class Class whose methods to decorate. decorator : function Decorator to apply to methods testmatch : compiled regexp or str, optional The regular expression. Default value is None, in which case the nose default (``re.compile(r'(?:^|[\b_\.%s-])[Tt]est' % os.sep)``) is used. If `testmatch` is a string, it is compiled to a regular expression first. Nz(?:^|[\\b_\\.%s-])[Tt]estr) isfunctioncompat_func_name_)recompilersep__dict__inspectrvaluesr+rrIAttributeErrorsearchrrsetattr) cls decorator testmatchcls_attrr_mmethodsfunctionfuncnames rPr r s.JJ;bffDE JJy) ||H#$OO-@-bBr-G@ x!344#44#,,   H % %h.A.A#.F.F C9X#6 7 A   s$&C::C:C?& C?? D  D c[R"S5nURURpT[ USUS3S5nSn[ 5nXq:aUS- n[ XeU5 Xq:aM[ 5U- nSU-$)a Return elapsed time for executing code in the namespace of the caller. The supplied code string is compiled with the Python builtin ``compile``. The precision of the timing is 10 milli-seconds. If the code will execute fast on this timescale, it can be executed many times to get reasonable timing accuracy. Parameters ---------- code_str : str The code to be timed. times : int, optional The number of times the code is executed. Default is 1. The code is only compiled once. label : str, optional A label to identify `code_str` with. This is passed into ``compile`` as the second argument (for run-time error messages). Returns ------- elapsed : float Total elapsed time in seconds for executing `code_str` `times` times. Examples -------- >>> times = 10 >>> etime = np.testing.measure('for i in range(1000): np.sqrt(i**2)', times=times) >>> print("Time for a single execution : ", etime / times, "s") # doctest: +SKIP Time for a single execution : 0.005 s rz Test name: rrkrg{Gz?)rrf_localsrrr!rk) code_strtimeslabelframelocsglobscoderelapseds rPr'r's|B MM! E..%//% 8{5'3V rOc[(dgSSKnSSKnUR"S5R SS5nUnSnUR "5 [ R"U5n[S5H nU"X45nM [[ R"U5U:5 UR"5 Ag!UR"5 f=f)z[ Check that ufuncs don't mishandle refcount of object `1`. Used in a few regression tests. TrNi'rr) r5gcrQr reshapedisablerr^rr(enable) oprrbcrrcjds rP_assert_valid_refcountr1s <  )$$S#.A A AJJL __Q rA1A"b()   s AB22Cc ^^^^ SnSSKm UUU U4Sjn T R"U5T R"U5pSTSSTS3n [XU[U5XjTUS9 g) u Raises an AssertionError if two objects are not equal up to desired tolerance. Given two array_like objects, check that their shapes and all elements are equal (but see the Notes for the special handling of a scalar). An exception is raised if the shapes mismatch or any values conflict. In contrast to the standard usage in numpy, NaNs are compared like numbers, no assertion is raised if both objects have NaNs in the same positions. The test is equivalent to ``allclose(actual, desired, rtol, atol)`` (note that ``allclose`` has different default values). It compares the difference between `actual` and `desired` to ``atol + rtol * abs(desired)``. Parameters ---------- actual : array_like Array obtained. desired : array_like Array desired. rtol : float, optional Relative tolerance. atol : float, optional Absolute tolerance. equal_nan : bool, optional. If True, NaNs will compare equal. err_msg : str, optional The error message to be printed in case of failure. verbose : bool, optional If True, the conflicting values are appended to the error message. strict : bool, optional If True, raise an ``AssertionError`` when either the shape or the data type of the arguments does not match. The special handling of scalars mentioned in the Notes section is disabled. .. versionadded:: 2.0.0 Raises ------ AssertionError If actual and desired are not equal up to specified precision. See Also -------- assert_array_almost_equal_nulp, assert_array_max_ulp Notes ----- When one of `actual` and `desired` is a scalar and the other is array_like, the function performs the comparison as if the scalar were broadcasted to the shape of the array. This behaviour can be disabled with the `strict` parameter. Examples -------- >>> x = [1e-5, 1e-3, 1e-1] >>> y = np.arccos(np.cos(x)) >>> np.testing.assert_allclose(x, y, rtol=1e-5, atol=0) As mentioned in the Notes section, `assert_allclose` has special handling for scalars. Here, the test checks that the value of `numpy.sin` is nearly zero at integer multiples of π. >>> x = np.arange(3) * np.pi >>> np.testing.assert_allclose(np.sin(x), 0, atol=1e-15) Use `strict` to raise an ``AssertionError`` when comparing an array with one or more dimensions against a scalar. >>> np.testing.assert_allclose(np.sin(x), 0, atol=1e-15, strict=True) Traceback (most recent call last): ... AssertionError: Not equal to tolerance rtol=1e-07, atol=1e-15 (shapes (3,), () mismatch) ACTUAL: array([ 0.000000e+00, 1.224647e-16, -2.449294e-16]) DESIRED: array(0) The `strict` parameter also ensures that the array data types match: >>> y = np.zeros(3, dtype=np.float32) >>> np.testing.assert_allclose(np.sin(x), y, atol=1e-15, strict=True) Traceback (most recent call last): ... AssertionError: Not equal to tolerance rtol=1e-07, atol=1e-15 (dtypes float64, float32 mismatch) ACTUAL: array([ 0.000000e+00, 1.224647e-16, -2.449294e-16]) DESIRED: array([0., 0., 0.], dtype=float32) TrNcP>TRRRXTTTS9$)N)rtolatolr;)_corenumericisclose)rrrr;rrs rPrd assert_allclose..compares.xx''4d1:(< >> x = np.array([1., 1e-10, 1e-20]) >>> eps = np.finfo(x.dtype).eps >>> np.testing.assert_array_almost_equal_nulp(x, x*eps/2 + x) >>> np.testing.assert_array_almost_equal_nulp(x, x*eps + x) Traceback (most recent call last): ... AssertionError: Arrays are not equal to 1 ULP (max is 2) TrNzArrays are not equal to z ULPz ULP (max is r)) rQrspacingwhererrr nulp_diffrf) rrnulpriraxayrefrhmax_nulps rPr)r)sb B B BHHRWb56 6C 66"&&-3& ' ' ??1  !3!3,TF$7Cvvio.H,TF-|1MCS!! (rOcSnSSKn[XU5nUR"Xb:*5(d[SX%R"U54-5eU$)a Check that all items of arrays differ in at most N Units in the Last Place. Parameters ---------- a, b : array_like Input arrays to be compared. maxulp : int, optional The maximum number of units in the last place that elements of `a` and `b` can differ. Default is 1. dtype : dtype, optional Data-type to convert `a` and `b` to if given. Default is None. Returns ------- ret : ndarray Array containing number of representable floating point numbers between items in `a` and `b`. Raises ------ AssertionError If one or more elements differ by more than `maxulp`. Notes ----- For computing the ULP difference, this API does not differentiate between various representations of NAN (ULP difference between 0x7fc00000 and 0xffc00000 is zero). See Also -------- assert_array_almost_equal_nulp : Compare two arrays relatively to their spacing. Examples -------- >>> a = np.linspace(0., 1., 100) >>> res = np.testing.assert_array_max_ulp(a, np.arcsin(np.sin(a))) TrNzCArrays are not almost equal up to %g ULP (max difference is %g ULP))rQrrrfr)rrmaxulprrirrets rPr+r+sWT A% C 66#- >$ffSk234 4 JrOc^SSKmU(a!TR"XS9nTR"XS9nO$TR"U5nTR"U5nTR"X5nTR"U5(dTR"U5(a [ S5eTR "U/US9nTR "U/US9nTR UTR"U5'TR UTR"U5'URUR:Xd'[SUR<SUR<35eU4Sjn[U5n[U5nU"XVU5$)aFor each item in x and y, return the number of representable floating points between them. Parameters ---------- x : array_like first input array y : array_like second input array dtype : dtype, optional Data-type to convert `x` and `y` to if given. Default is None. Returns ------- nulp : array_like number of representable floating point numbers between each item in x and y. Notes ----- For computing the ULP difference, this API does not differentiate between various representations of NAN (ULP difference between 0x7fc00000 and 0xffc00000 is zero). Examples -------- # By definition, epsilon is the smallest number such as 1 + eps != 1, so # there should be exactly one ULP between 1 and 1 + eps >>> nulp_diff(1, 1 + np.finfo(x.dtype).eps) 1.0 rNr&z'_nulp not implemented for complex arrayz#Arrays do not have the same shape: z - cN>TR"X- US9nTR"U5$Nr&)rr)rxryvdtrvrs rP_diffnulp_diff.._diffas#zz"'-vvd|rO) rQr common_typerrrrrr*r integer_repr)rrrtrrrrs @rPrr+s@ JJq & JJq & JJqM JJqM qA qR__Q//!"KLL !AA !AAVVAbhhqkNVVAbhhqkN 77agg ''177,- - aB aB  rOc~URU5nURS:XdX#US:- X3S:'U$US:aX#- nU$)Nrr)viewr,)rrcomprs rP _integer_reprrjsN B GGqLrAvJ&6 I 6B IrOcSSKnURUR:Xa&[XRUR"S55$URUR :Xa&[XR UR "S55$URUR:Xa&[XRUR"S55$[SUR35e)zMReturn the signed-magnitude interpretation of the binary representation of x.rNiilzUnsupported dtype ) rQrfloat16rint16r int32rint64r)rrs rPrrysww"**Q"((6*:;; BJJ Q"((6*:;; BJJ Q"((6*:;;-aggY788rOc## Sn[5nURU5nSv [U5S:dUbSU3OSn[SU-5eSSS5 g!,(df  g=f7f)NTr when calling r`zNo warning raised)r7recordrrf) warning_classrrisuprname_strs rP_assert_warns_contextr sc   JJ} % 1vz262Bv.H !4x!?@ @   s A'=A A' A$ A'c U(dU(d [U5$[U5S:aSU;a [S5e[S5eUSnUSSn[XRS9 U"U0UD6sSSS5 $!,(df  g=f)a Fail unless the given callable throws the specified warning. A warning of class warning_class should be thrown by the callable when invoked with arguments args and keyword arguments kwargs. If a different type of warning is thrown, it will not be caught. If called with all arguments other than the warning class omitted, may be used as a context manager:: with assert_warns(SomeWarning): do_something() The ability to be used as a context manager is new in NumPy v1.11.0. Parameters ---------- warning_class : class The class defining the warning that `func` is expected to throw. func : callable, optional Callable to test *args : Arguments Arguments for `func`. **kwargs : Kwargs Keyword arguments for `func`. Returns ------- The value returned by `func`. Examples -------- >>> import warnings >>> def deprecated_func(num): ... warnings.warn("Please upgrade", DeprecationWarning) ... return num*num >>> with np.testing.assert_warns(DeprecationWarning): ... assert deprecated_func(4) == 16 >>> # or passing a func >>> ret = np.testing.assert_warns(DeprecationWarning, deprecated_func, 4) >>> assert ret == 16 rmatchzAassert_warns does not use 'match' kwarg, use pytest.warns insteadz(assert_warns(...) needs at least one argrNr)r r RuntimeErrorrI)rrrrs rPr,r,sV $]33 TQ f + EFF 7D 8D }== AT$V$ B A As "A44 Bc## Sn[R"SS9n[R"S5 Sv [U5S:aUbSU3OSn[ SUSU35eSSS5 g!,(df  g=f7f) NTralwaysrrr`z Got warningsr)warningscatch_warnings simplefilterrrf)rrirr s rP_assert_no_warnings_contextrsr   -h' q6A:262Bv.H <zA3!?@ @  . - -sA9AA( A9( A62A9cU(d [5$USnUSSn[URS9 U"U0UD6sSSS5 $!,(df  g=f)a Fail if the given callable produces any warnings. If called with all arguments omitted, may be used as a context manager:: with assert_no_warnings(): do_something() The ability to be used as a context manager is new in NumPy v1.11.0. Parameters ---------- func : callable The callable to test. \*args : Arguments Arguments passed to `func`. \*\*kwargs : Kwargs Keyword arguments passed to `func`. Returns ------- The value returned by `func`. rrNr)rrIrrrs rPr-r-sI2 *,, 7D 8D $$-- 8T$V$ 9 8 8s A Abinaryc #,^^ ^ # SnSn[S5GHym [T S-[T S-U55GHTm US:XaUU U 4Sjn[T 4TS9T SnXe"5UT T T TS 4-4v U"5nXwUT T T TS 4-4v US SU"5SS UT S -T T S - TS 4-4v USS U"5S SUT T S -T S - TS 4-4v U"5SS U"5S SUT T S -T S - TS 4-4v U"5S SU"5SS UT S -T T S - TS 4-4v US:XdMUU U 4SjnUU U 4Sjn [T 4TS9T SnXh"5U "5UT T T T TS 4-4v U"5nXwU "5UT T T T TS4-4v U "5nXx"5XtT T T T TS4-4v US SU"5SS U "5SS UT S -T T T S - TS 4-4v USS U"5S SU "5SS UT T S -T T S - TS 4-4v USS U"5SS U "5S SUT T T S -T S - TS 4-4v U"5S SU"5SS U "5SS UT S -T T T S - TS 4-4v U"5SS U"5S SU "5SS UT T S -T T S - TS 4-4v U"5SS U"5SS U "5S SUT T T S -T S - TS 4-4v GMW GM| g7f)a generator producing data with different alignment and offsets to test simd vectorization Parameters ---------- dtype : dtype data type to produce type : string 'unary': create data for unary operations, creates one input and output array 'binary': create data for unary operations, creates two input and output array max_size : integer maximum size of data to produce Returns ------- if type is 'unary' yields one output, one input array and a message containing information on the data if type is 'binary' yields one output array, two input array and a message containing information on the data z,unary offset=(%d, %d), size=%d, dtype=%r, %sz1binary offset=(%d, %d, %d), size=%d, dtype=%r, %srRrnunaryc>[TTS9TS$rr rorsrPrX%_gen_alignment_data..sfQe4QR8rOr&Nz out of placezin placerraliasedrc>[TTS9TS$rrrsrPrXr!&vau5ab9rOc>[TTS9TS$rrrsrPrXr!'r$rOz in place1z in place2)rrr ) rrmax_sizeufmtbfmtinpr(rinp1inp2r rs ` @@rP_gen_alignment_datar,s2 :D >D 1Xq1uc!a%23Aw8QD.qr235$!Q5.)I"IIIEDAq!UJ#????!"gsuSbz4UAq1ue^<,===#2hab 4Aq1ue^<,===eCRj#%)TAq1ueY7.888eABisTUAq1ueY7.888x99QD.qr24646D1a7-888FDFD1a 4%555F1a 4%555!"gtvcr{DF3BKUAq!a%?:@@@#2hqr DF3BKAq!a%?:@@@#2hs TVABZ1q5!a%?:@@@fQRj$&"+tvcr{DUAq!a% :=;;;fSbk46!":tvcr{DAq!a% :=;;;fSbk46#2;qr D1q5!a% :=;;;K4s DJFJc\rSrSrSrSrg)r/i?z/Ignoring this exception due to disabled featurerGNrHrGrOrPr/r/?s5rOr/c/# [U0UD6nUv [R"U5 g![R"U5 f=f7f)zContext manager to provide a temporary test folder. All arguments are passed as this to the underlying tempfile.mkdtemp function. N)rshutilrmtree)rrtmpdirs rPr3r3Ds8d %f %F  f fs A*AAAc/# [U0UD6up#[R"U5 Uv [R"U5 g![R"U5 f=f7f)aContext manager for temporary files. Context manager that returns the path to a closed temporary file. Its parameters are the same as for tempfile.mkstemp and are passed directly to that function. The underlying file is removed when the context is exited, so it should be closed at that time. Windows does not allow a temporary file to be opened if it is already open, so the underlying file must be closed after opening before it can be opened again. N)rrcloseremove)rrfdr|s rPr2r2SsC''HBHHRL  $ $s$AAAAAcL^\rSrSrSrSrSU4SjjrU4SjrU4SjrSr U=r $) r0iiaContext manager that resets warning registry for catching warnings Warnings can be slippery, because, whenever a warning is triggered, Python adds a ``__warningregistry__`` member to the *calling* module. This makes it impossible to retrigger the warning in this module, whatever you put in the warnings filters. This context manager accepts a sequence of `modules` as a keyword argument to its constructor and: * stores and removes any ``__warningregistry__`` entries in given `modules` on entry; * resets ``__warningregistry__`` to its previous state on exit. This makes it possible to trigger any warning afresh inside the context manager without disturbing the state of warnings outside. For compatibility with Python 3.0, please consider all arguments to be keyword-only. Parameters ---------- record : bool, optional Specifies whether warnings should be captured by a custom implementation of ``warnings.showwarning()`` and be appended to a list returned by the context manager. Otherwise None is returned by the context manager. The objects appended to the list are arguments whose attributes mirror the arguments to ``showwarning()``. modules : sequence, optional Sequence of modules for which to reset warnings registry on entry and restore on exit. To work correctly, all 'ignore' filters should filter by one of these modules. Examples -------- >>> import warnings >>> with np.testing.clear_and_catch_warnings( ... modules=[np._core.fromnumeric]): ... warnings.simplefilter('always') ... warnings.filterwarnings('ignore', module='np._core.fromnumeric') ... # do something that raises a warning but ignore those in ... # np._core.fromnumeric rGc>[U5RUR5Ul0Ul[ TU]US9 g)Nr)setunion class_modulesmodules_warnreg_copiessuper__init__)rrr; __class__s rPr>!clear_and_catch_warnings.__init__s77|))$*<*<= ! 'rOc>URHOn[US5(dMURnUR5URU'UR 5 MQ [ TU]5$N__warningregistry__)r;r+rCcopyr<clearr= __enter__)rmodmod_regr?s rPrF"clear_and_catch_warnings.__enter__sY<[TU]"U6 URHgn[US5(aURR 5 X R ;dM?URRUR U5 Mi grB)r=__exit__r;r+rCrEr<update)rexc_inforGr?s rPrK!clear_and_catch_warnings.__exit__si (#<rFrKrN __classcell__)r?s@rPr0r0is&(RM( #JJrOr0cz\rSrSrSrSSjrSr\SSS4Sjr\SS4S jr \SS4S jr S r S r SS .Sjr SrSrg)r7ia Context manager and decorator doing much the same as ``warnings.catch_warnings``. However, it also provides a filter mechanism to work around https://bugs.python.org/issue4180. This bug causes Python before 3.4 to not reliably show warnings again after they have been ignored once (even within catch_warnings). It means that no "ignore" filter can be used easily, since following tests might need to see the warning. Additionally it allows easier specificity for testing warnings and can be nested. Parameters ---------- forwarding_rule : str, optional One of "always", "once", "module", or "location". Analogous to the usual warnings module filter mode, it is useful to reduce noise mostly on the outmost level. Unsuppressed and unrecorded warnings will be forwarded based on this rule. Defaults to "always". "location" is equivalent to the warnings "default", match by exact location the warning warning originated from. Notes ----- Filters added inside the context manager will be discarded again when leaving it. Upon entering all filters defined outside a context will be applied automatically. When a recording filter is added, matching warnings are stored in the ``log`` attribute as well as in the list returned by ``record``. If filters are added and the ``module`` keyword is given, the warning registry of this module will additionally be cleared when applying it, entering the context, or exiting it. This could cause warnings to appear a second time after leaving the context if they were configured to be printed once (default) and were already printed before the context was entered. Nesting this context manager will work as expected when the forwarding rule is "always" (default). Unfiltered and unrecorded warnings will be passed out and be matched by the outer level. On the outmost level they will be printed (or caught by another warnings context). The forwarding rule argument can modify this behaviour. Like ``catch_warnings`` this context manager is not threadsafe. Examples -------- With a context manager:: with np.testing.suppress_warnings() as sup: sup.filter(DeprecationWarning, "Some text") sup.filter(module=np.ma.core) log = sup.record(FutureWarning, "Does this occur?") command_giving_warnings() # The FutureWarning was given once, the filtered warnings were # ignored. All other warnings abide outside settings (may be # printed/error) assert_(len(log) == 1) assert_(len(sup.log) == 1) # also stored in log attribute Or as a decorator:: sup = np.testing.suppress_warnings() sup.filter(module=np.ma.core) # module must match exactly @sup def some_function(): # do something which causes a warning in np.ma.core pass cNSUl/UlUS;a [S5eXlg)NF>oncermodulelocationzunsupported forwarding rule.)_entered _suppressionsr_forwarding_rule)rforwarding_rules rPr>suppress_warnings.__init__s.   "J J;< < /rOc[[S5(a[R"5 gURH0n[US5(dMURR 5 M2 g)N_filters_mutatedrC)r+rr[ _tmp_modulesrCrE)rrSs rP_clear_registries#suppress_warnings._clear_registriessS 8/ 0 0  % % ' ''Fv455**002(rOr`NFc:U(a/nOSnUR(aUc[R"SXS9 O`URR SS5S-n[R"SXUS9 UR R U5 UR5 URRX[R"U[R5X445 U$URRX[R"U[R5X445 U$)Nrcategorymessage.\.$rarbrS)rUrfilterwarningsrIreplacer\addr]_tmp_suppressionsrrrIrV)rrarbrSr module_regexs rP_filtersuppress_warnings._filter s FF ==~''xB &66sEBSH ''x')!!%%f-&&(  " " ) )BJJw$=vN P      % %BJJw$=vN P rOc&URXUSS9 g)a' Add a new suppressing filter or apply it if the state is entered. Parameters ---------- category : class, optional Warning class to filter message : string, optional Regular expression matching the warning message. module : module, optional Module to filter for. Note that the module (and its file) must match exactly and cannot be a submodule. This may make it unreliable for external modules. Notes ----- When added within a context, filters are only added inside the context and will be forgotten when the context is exited. FrarbrSrNrmrrarbrSs rPfiltersuppress_warnings.filter$ s( h!  #rOc$URXUSS9$)a Append a new recording filter or apply it if the state is entered. All warnings matching will be appended to the ``log`` attribute. Parameters ---------- category : class, optional Warning class to filter message : string, optional Regular expression matching the warning message. module : module, optional Module to filter for. Note that the module (and its file) must match exactly and cannot be a submodule. This may make it unreliable for external modules. Returns ------- log : list A list which will be filled with all matched warnings. Notes ----- When added within a context, filters are only added inside the context and will be forgotten when the context is exited. Trprqrrs rPrsuppress_warnings.record; s!6||Xv#') )rOcUR(a [S5e[RUl[R UlUR SS[lSUl/Ul[5Ul [5Ul /Ul URHyupp4nUbUSS2 Uc[R"SXS9 M)URRSS5S-n[R"SXUS9 URR!U5 M{ UR"[lUR%5 U$) Nz%cannot enter suppress_warnings twice.Trr`rcrdrerf)rUrr showwarning _orig_showfilters_filtersrjr8r\ _forwardedlogrVrgrIrhri _showwarningr])rcatmessrrGr}rls rPrFsuppress_warnings.__enter__Y s ==FG G".. (( ==+ !#E%&*&8&8 "CqsF{''s: #||33C?#E ''s')!!%%c*'9 $00   rOcUR[lUR[lUR 5 SUlU?U?g)NF)ryrrxr{rzr]rU)rrMs rPrKsuppress_warnings.__exit__y s7#==   O MrO) use_warnmsgcURUR-SSS2Huppn [X(5(dMU RURS5cM:U c?U b:[ XUU40UD6n UR RU 5 U RU 5 gU RRU5(dMU b:[ XUU40UD6n UR RU 5 U RU 5 g URS:Xa-UcUR"XX4/UQ70UD6 gURU5 gURS:XaURU4nO>URS:XaURX#4nOURS:XaURX#U4nWUR;agURRU5 UcUR"XX4/UQ70UD6 gURU5 g)NrrrrRrSrT)rVrj issubclassr rrr}rr}rrrWry _orig_showmsgr|ri)rrbrarlinenorrrrrpatternrGrecrh signatures rPr~suppress_warnings._showwarning s""T%;%;;TrT*C %CG#8))MM',,q/2>;,W-3?7=?, 3\\,,X66,W-3?7=?, 3+*C2  H ,"81!%1)/1 "";/   F * x0I  " "h . x:I  " "j 0 x6BI  '  I&   OOGx &$ &$ &   { +rOc4^^[T5UU4Sj5nU$)zG Function decorator to apply certain suppressions to a whole function. cN>T T"U0UD6sSSS5 $!,(df  g=frrG)rrrrs rPnew_func,suppress_warnings.__call__..new_func sT,V,s $r)rrrs`` rP__call__suppress_warnings.__call__ s" t -  -rO) rUr{r|rWryrVr\rjr})r)rIrJrKrLrMr>r]WarningrmrsrrFrKr~rrNrGrOrPr7r7sZHR0 3 '42&r$#.&r$)<@)-1,f rOr7c #n# Sn[(dSv g[[R"55 [R"5 [R "5n[ S5Hn[R"5S:XdM O [S5e[R"[R5 Sv [R"5n[RSSn[RSS2 [R"U5 [R"5 U(aFUbSU3OSn[SRUU[U5SR!SU5555eg![RSS2 [R"U5 [R"5 f=f7f) NTrrz]Unable to fully collect garbage - perhaps a __del__ method is creating more reference cycles?rr`zXReference cycles were found{}: {} objects were collected, of which {} are shown below:{}c 3# UHXnSR[U5R[U5[R "U5R SS55v MZ g7f)z {} object with id={}: {}rz N)rzrrIidrpformatrh).0r s rP /_assert_no_gc_cycles_context.. sX 1! 8>>Q((1q)11$A 1sA A")r5r(r isenabledr get_debugrcollectr set_debug DEBUG_SAVEALLgarbagerrfrzrr)rrigc_debugrn_objects_in_cyclesobjects_in_cyclesr s rP_assert_no_gc_cycles_contextr sI <  BLLNJJL||~HsAzz|q 56 6 R%%& !jjlJJqM JJqM X .2.>^D6*B - V#%& 1     JJqM X s'AF5%E2AE2&B F52AF22F5cU(d [5$USnUSSn[URS9 U"U0UD6 SSS5 g!,(df  g=f)a Fail if the given callable produces any reference cycles. If called with all arguments omitted, may be used as a context manager:: with assert_no_gc_cycles(): do_something() Parameters ---------- func : callable The callable to test. \*args : Arguments Arguments passed to `func`. \*\*kwargs : Kwargs Keyword arguments passed to `func`. Returns ------- Nothing. The result is deliberately discarded to ensure that all cycles are found. rrNr)rrIrs rPr9r9 sI0 +-- 7D 8D %4== 9 df : 9 9s A Ac[R"5 [(aU[R"5 [R"5 [R"5 [R"5 gg)a Break reference cycles by calling gc.collect Objects can call other objects' methods (for instance, another object's __del__) inside their own __del__. On PyPy, the interpreter only runs between calls to gc.collect, so multiple calls are needed to completely release all cycles. N)rrr4rGrOrPr:r: s;JJLw    rOc ^^SSKmUU4SjnU$)z:Decorator to skip a test if not enough memory is availablerNc6>^[T5UUU4Sj5nU$)Nc>[T5nUbTRU5 T"U0UD6$![a TRS5 gf=f)NzMemoryError raised)check_free_memoryskip MemoryErrorxfail)rkwrh free_bytesrpytests rPwrapper3requires_memory..decorator..wrapper- sM#J/C C  3Q~"~% 3 12 3s*AAr)rrrrs` rPr"requires_memory..decorator, s t 3  3rO)r)rrrs` @rPrequires_memoryr( s  rOcSn[RRU5nUb[U5nUS- SUS3nO$[ 5nUcSnS nOUS- nUS- nUS US 3nX0:aU$S$![an[ SUSU35eSnAff=f) z Check whether `free_bytes` amount of memory is currently free. Returns: None if enough memory available, otherwise error message NPY_AVAILABLE_MEMNzInvalid environment variable rgeAz@ GB memory required, but environment variable NPY_AVAILABLE_MEM=z setzCould not determine available memory; set NPY_AVAILABLE_MEM environment variable (e.g. NPY_AVAILABLE_MEM=16GB) to run the test.rz GB memory required, but z GB available)renvironget _parse_sizer_get_mem_available)renv_var env_valuemem_freerrh free_bytes_gb mem_free_gbs rPrr> s "G w'I O"9-Hs"#$$$-;d4&'  CH&,M"S.K"O#<[MWC'31T1% O?@@ uQWWQZ 8GGAJ#77 88rOcSSKnUR5R$![[4a Of=f[ R RS5(a0n[S5nUHFnUR5n[US5S-XSRS5R5'MH SSS5 O!,(df  O=fSU;aUS$US US -$g) z5Return available memory in bytes, or None if unknown.rNrz /proc/meminforr: memavailablememfreecached) psutilvirtual_memory available ImportErrorrrplatformrrrrrstripr)rinforlineps rPrrm s $$&000  (    ||w'' / "aJJL03AaD D0@qTZZ_**,-# " " T !' ' ?T(^3 3 s 33'A B== C c^^[[S5(dT$[T5U4Sj5nU$)z Decorator to temporarily turn off tracing for the duration of a test. Needed in tests that check refcounting, otherwise the tracing itself influences the refcounts gettracec>[R"5n[R"S5 T"U0UD6[R"U5 $![R"U5 f=fr)rrsettrace)rroriginal_tracers rPr_no_tracing..wrapper sE \\^N - T"T,V, ^, ^,s A A$)r+rr)rrs` rP _no_tracingr s4 3 # # t -  -rOc~[R"S5RS5SnU$![a SnU$f=f)NCS_GNU_LIBC_VERSIONrr0.0)rconfstrrsplitr)vers rP_get_glibc_versionr sHjj./66s;A> J  Js (, <<c4[S:g=(a [U:$)Nr) _glibcverrs rPrXrX syE1Ci!mCrOc[U5GHn[RRUS9nUc/nOU"5nU(a'[R "U5n UR U 5 U(a [U5V s/sH oU /UQ7PM n n O[U5V s/sHo/UQ7PM n n /n U H!n U R UR"U 65 M# [U 5U:aU(aW R5 U HnUR5 M SSS5 GM gs sn fs sn f![W 5U:aU(aW R5 fff=f!,(df  GM`=f)z&Runs a function many times in parallel) max_workersN) r concurrentfuturesThreadPoolExecutor threadingBarrierrsubmitrabortr)rr pass_count pass_barrierouter_iterations prepare_argsrtperbarrierrall_argsrargrs rPrCrC s:# $  33 3L##~#++K8 G$6;K6HI6H1,t,6HI383EF3EaMDM3EF $#CNN3::s#34$w<+-,MMO )ML%JF w<+-,MMO3?-%MLsBAE=D% ED*,E/)D/?E% E/*EE E, cU[LdUS:wa[RRXS9$[RRUS9$)Nunsetr%coerce)r)rrdtypes StringDTypers rPget_stringdtype_dtyper sAEY'1yy$$y$HHyy$$F$33rO)r`)NrNN)pythonr)zItems are not equal:Trrc)r`T)r`T)r`Tr`TT)r r`T)NTr)rN)gHz>rTr`T)r)rcFFrN)T)rMrrpathlibrrrrXr functoolsrrr/r0tempfilerr unittest.caserrr sysconfigconcurrent.futuresrrimportlib.metadata importlibrQrrr r r r r rrrrrrnumpy.linalg._umath_linalg numpy._utilsrnumpy._core.tests._natyperior__all__rr1KnownFailureTestr&Pathr}parentrBmetadata distributionnp_distrA version_infoorigindir_infoeditabler@jsonrUloads read_textr locate_filePackageNotFoundErrorr{r6implementationrr4r+r<r5r5linalg _umath_linalg_ilp64r;r=get_config_var_vrr?ritemsizerDr(rr"getpidr!rrr#rrr8rrrr%rr$r>unittestTestCaserrrr*r r'rr.r)r+rrrcontextmanagerr r,rr-r,r/r3r2rr0r7rr9r:rrrrrrr_glibc_older_thanrCrrGrOrPr3sJ  $ %"# FFF((!*+ " I )  \\"++ & - -   --g6GL    w &!..11::K ZZ!!"34<FF!//22K 7..w7:E     4 4   ! !V + C. / sM40<NY ||))00  o.4" R<G9++,=>? 88BGG  % % *#(77d?;??C$8E  \\"1 "( U ; "<<w!' }E:r<* 8+AGH:OeOd&-R{/|AC $a"HMO@DG#(0EGTC:)4'J~(#~(K~(BC:)4'JBD&*p Kp fp+p+fD"N+K\!, X    E],: S , ^+\ 4CG(,j(8=j(Z<"~1h<~  9 AA8%v AA%D&HrB;J i     *?Jx66?JDSSl 0 0 fB$,2> 9 0(  D2767":4gS  ..'!&&L;'s+ Q>+0Q/AQ//Q;:Q;>R R