a p=icM@sdZddlZddlZddlZddlZddlZddlZddlZddlm Z m Z ddl Z ddl Z ddl mZmZddlmZddlmZddlZddlZddlmZmZmZmZmZmZmZmZddlZddl m!Z!gd Z"Gd d d e#Z$e$Z%dZ&e'd kZ(e)ed Z*e+eddduoe* Z,ej-j.j/Z0ddZ1dddZ2ddZ3ddZ4ddZ5ej6dkrtdddZ7ddd Z8n6ejdd!d"krd#e9d$fd%d Z8nd&d Z8ejdd!d"krd#e9d$gfd'd(Z:n gfd)d(Z:dd.d/Z;dd0d1Zdd7d8Z?dd:d;Z@ddd?ZBdd@dAZCdBdCZDdDdEZEddFdGZFdHdIZGddlHZHGdJdKdKeHjIZJeJdLZKdMdNZLdOdPZMddQdRZNddTdUZOdVdWZPddYdZZQdd[d\ZRdd]d^ZSdd_d`ZTdadbZUdcddZVe jWddedfZXdgdhZYe jWddidjZZdkdlZ[edmdnfdodpZ\Gdqdrdre#Z]e jWdsdtZ^e jWdudvZ_Gdwdxdxej`ZaGdydzdzZbe jWdd{d|Zcd}d~ZdddZeddZfddZgddZhddZiddZjddZkekZlddZmdS)z* Utility function to facilitate testing. N)partialwraps)mkdtempmkstemp)SkipTest)WarningMessage)intpfloat32emptyarange array_reprndarrayisnatarray)StringIO)' assert_equalassert_almost_equalassert_approx_equalassert_array_equalassert_array_lessassert_string_equalassert_array_almost_equal assert_raises build_err_msgdecorate_methodsjiffiesmemusageprint_assert_equalraisesrundocs runstringverbosemeasureassert_assert_array_almost_equal_nulpassert_raises_regexassert_array_max_ulp assert_warnsassert_no_warningsassert_allcloseIgnoreExceptionclear_and_catch_warningsrKnownFailureExceptiontemppathtempdirIS_PYPY HAS_REFCOUNTsuppress_warningsassert_array_compareassert_no_gc_cycles break_cycles HAS_LAPACK64 IS_PYSTONc@seZdZdZdS)r,z= %d.%d.%d for tests - see https://nose.readthedocs.io)nose ImportErrorZ__versioninfo__)Z nose_is_goodZminimum_nose_versionrAmsgr<r<r= import_nose8s    rDcCs6d}|s2z |}Wnty(|}Yn0t|dS)aI 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)valrC__tracebackhide__Zsmsgr<r<r=r#Ns    r#cCs.ddlm}||}t|ttr*td|S)alike isnan, but always raise an error if type not supported instead of returning a TypeError object. Notes ----- isnan and other ufunc sometimes return a NotImplementedType object instead of raising any exception. This function is a wrapper to make sure an exception is always raised. This should be removed once this problem is solved at the Ufunc level.r)isnanz!isnan not supported for this type) numpy.corerJ isinstancetypeNotImplementedrF)xrJstr<r<r=gisnanbs rQcCs\ddlm}m}|dd.||}t|ttr:tdWdn1sN0Y|S)alike isfinite, but always raise an error if type not supported instead of returning a TypeError object. Notes ----- isfinite and other ufunc sometimes return a NotImplementedType object instead of raising any exception. This function is a wrapper to make sure an exception is always raised. This should be removed once this problem is solved at the Ufunc level.r)isfiniteerrstateignoreinvalidz$isfinite not supported for this typeN)rKrRrSrLrMrNrF)rOrRrSrPr<r<r= gisfinitets  &rWcCs\ddlm}m}|dd.||}t|ttr:tdWdn1sN0Y|S)alike isinf, but always raise an error if type not supported instead of returning a TypeError object. Notes ----- isinf and other ufunc sometimes return a NotImplementedType object instead of raising any exception. This function is a wrapper to make sure an exception is always raised. This should be removed once this problem is solved at the Ufunc level.r)isinfrSrTrUz!isinf not supported for this typeN)rKrXrSrLrMrNrF)rOrXrSrPr<r<r=gisinfs  &rYntc Csddl}|dur|j}||||d||f}|}z^|||} z6|||| |\} } | W|| W||S|| 0W||n ||0dS)Nr) win32pdh PDH_FMT_LONGZMakeCounterPathZ OpenQueryZ AddCounterZCollectQueryDataZGetFormattedCounterValueZ RemoveCounterZ CloseQuery) objectcounterinstanceZinumformatmachiner\pathZhqZhcrMrHr<r<r=GetPerformanceAttributess&      rdpythoncCsddl}tdd|||jdS)NrProcessz Virtual Bytes)r\rdr]) processNamer`r\r<r<r=rs rlinuxz/proc/z/statcCs`zFt|d}|d}Wdn1s00Yt|dWStyZYdS0dS)zM Return virtual memory size in bytes of the running python. r N)openreadlinesplitint Exception)_proc_pid_statflr<r<r=rs  , cCstdS)zK Return memory usage of running python. [Not implemented] N)NotImplementedErrorr<r<r<r=rscCsddl}|s||zFt|d}|d}Wdn1sJ0Yt|dWStytd||dYS0dS) 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. rNrjrk d)timeappendrmrnrorprq)rr _load_timeryrsrtr<r<r=rs , rcCs2ddl}|s||td||dS)rvrNrx)ryrzrp)r{ryr<r<r=rsItems are not equal:TZACTUALZDESIREDc Csd|g}|rN|ddkrDt|dt|krD|dd|g}n |||rt|D]\}}t|tr|tt|d} nt} z | |} Wn<t y} z$dt |j d| d } WYd} ~ n d} ~ 00| dd krd | dd } | d 7} |d||d | q\d |S) N r[Orrk) precisionz[repr failed for : ]z...: )findlenrz enumeraterLr rr reprrqrMr8countjoin splitlines) Zarrayserr_msgheaderr!namesrrCiaZr_funcrjexcr<r<r=rs& "   .rc Csd}t|trt|ts(ttt|tt|t||||D]>\}}||vrbtt|t||||d|d||qFdSt|tt frt|tt frtt|t|||t t|D]&}t||||d|d||qdSddl m }m }m} ddlm} m} m} t||s4t||rBt||||St||g||d } z| |pf| |}Wnttfyd }Yn0|r | |r| |}| |}n|}d}| |r| |}| |}n|}d}zt||t||Wnty t| Yn0||||kr&t| zPt|}t|}t|jjt|jjk}|rt|rt|rlWdSt| WntttfyYn0zt|}t|}|r|rWdSt|}t|}|jjd vs|jjd vrtd |dkr|dkr| || |kst| Wntttfy8Yn0z||ksNt| WnFttfy}z(d |j dvrt| nWYd}~n d}~00dS)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. 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 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. Raises ------ AssertionError If actual and desired are not equal. 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]) Tzkey=rNzitem=r)r isscalarsignbit iscomplexobjrealimagr!FMmz0cannot compare to a scalar with a different typezelementwise == comparison)!rLdictrGrrMrritemslisttuplerangerKr rr numpy.librrrrr ValueErrorrFrnpasarraydtyperurQcharDeprecationWarning FutureWarningargs)actualdesiredrr!rIkrr rrrrrrC usecomplexactualractualidesiredrdesirediZisdesnatZisactnatZ dtypes_matchZisdesnanZisactnanZ array_actualZ array_desireder<r<r=rs2                     rcCs`d}ddl}||ks\t}|||d||||d|||t|dS)a Test if two objects are equal, and print an error message if test fails. The test is performed with ``actual == desired``. Parameters ---------- test_string : str The message supplied to AssertionError. actual : object The object to test for equality against `desired`. desired : object The expected result. Examples -------- >>> 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: )pprintrwriterGgetvalue) test_stringrrrIrrCr<r<r=rs     rc sd}ddlm}ddlm}m}m} z|p4|} WntyNd} Yn0fdd} | r|r|} | } n} d} |r|}| }n}d}z t| |dt| |dWntyt| Yn0t |t t fst |t t frt Szft r2t stsFtrftrZtszt| nkszt| Wd SWnttfyYn0td d  krt| d S) a 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) < 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: 6.66669964e-09 Max relative difference: 2.85715698e-09 x: array([1. , 2.333333333]) y: array([1. , 2.33333334]) Tr)r rFcsd}tg|dS)N*Arrays are not almost equal to %d decimals)r!r)r)rrdecimalrrr!r<r=_build_err_msg-s z+assert_almost_equal.._build_err_msg)rN?$@)rKr rrrrrrrGrLrrrrWrQrurFabs)rrrrr!rIr rrrrrrrrrr<rr=rsPE          rc Csd}ddl}tt||f\}}||kr*dS|jdd@d||||}|d|||}Wdn1s|0Yz ||}Wntyd}Yn0z ||} Wntyd} Yn0t ||g|d ||d } z`t |rt |sDt |st |r,t |r"t |s>t | n||ks>t | WdSWnt tfy^Yn0||| |d |d  krt | dS) aa 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 TrNrTrUg? gz-Items are not equal to %d significant digits:)rr!rr@)numpymapfloatrSrpowerfloorlog10ZeroDivisionErrorrrWrQrGrFru) rrZ significantrr!rIrscaleZ sc_desiredZ sc_actualrCr<r<r=rZsB:6         "rc % sd} ddlm} m} m} mmm} m}m}m }t |}t |}||}}dd}dd}| dffd d }z|j d kp|j d kp|j |j k}|st ||gd |j d |j ddd}t|d}||rH||rH|r|||| dd}|r||||fddddO}||||fddddO}n<||r||r|r|jj|jjkr|||tdd}|jdkr||||}}|jdkrWdSn |rWdS|||}t|tr|}| |g}n|}|}|dkr|j|jtd}|jdkr*|jn|j}d||}d|||g}| ddttt||}||} t|d||kr|dt | n|d| | |dk}!||!r| }"n|||!t||!}"t|d||kr|d t |"n|d | |"Wdn1s80YWdn1sX0Yd!d!!|7t ||gdd}t|WnTt"yddl#}#|#$}$d"|$d#t ||gdd}t"|Yn0dS)$NTr) r array2stringrJinfbool_rSallmaxobject_cSs |jjdvS)Nz?bhilqpBHILQPefdgFDGrrrOr<r<r=isnumbersz&assert_array_compare..isnumbercSs |jjdvS)Nrrrr<r<r=istimesz$assert_array_compare..istimenancsd}||}||}||kdkrPt||gd|dd}t|t|tsd|jdkrl|St|ts|jdkr|S|SdS)zHandling nan/inf. Combine results of running func on x and y, checking that they are True at the same locations. Tz x and y %s location mismatch:rOyr!rrrrN)rrrGrLboolndim)rOrfunchasvalrIZx_idZy_idrC)rrrrr!r<r=func_assert_same_poss" z2assert_array_compare..func_assert_same_posr<z (shapes z, z mismatch)rrF)rrcs | kSNr<Zxyrr<r=z&assert_array_compare..z+infcs | kSrr<rrr<r=rrz-infZNaTrrxz&Mismatched elements: {} / {} ({:.3g}%)rT)rrzMax absolute difference: zMax relative difference: rzerror during assertion: z )%rKrrrJrrrSrrrr asanyarrayshaperrGrrMrrsizerLrZravelsumrra contextlibsuppressrFrgetattrrzstrrr traceback format_exc)%Z comparisonrOrrr!rr equal_nan equal_infrIrrrJrSrrroxZoyrrrZcondrCZflaggedrHZreducedZ n_mismatchZ n_elementsZpercent_mismatchZremarkserrorZ max_abs_errorZnonzeroZ max_rel_errorrZefmtr<)rrrrrr!r=r2s,   %                 F  r2cCsd}ttj||||dddS)al 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. Parameters ---------- x : array_like The actual object to check. y : 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. 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 `x` and `y` 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. 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: 4.4408921e-16 Max relative difference: 1.41357986e-16 x: array([1. , 3.141593, nan]) y: 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) TzArrays are not equal)rr!rN)r2operator__eq__rOrrr!rIr<r<r=rWsN rc shd}ddlmmmm}ddlmddlmfdd}t |||||dd d S) 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 ---------- x : array_like The actual object to check. y : 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: 6.e-05 Max relative difference: 2.57136612e-05 x: array([1. , 2.33333, nan]) y: 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 x and y nan location mismatch: x: array([1. , 2.33333, nan]) y: array([1. , 2.33333, 5. ]) Tr)numberfloat_ result_typer) issubdtype)anyc szxt|st|rvt|}t|}||ks.comparer)rr!rrN) rKrrrrZnumpy.core.numerictypesrZnumpy.core.fromnumericrr2)rOrrrr!rIrrr<rr=rsM   rc Cs d}ttj||||ddddS)ag Raises an AssertionError if two array_like objects are not ordered by less than. Given two array_like objects, check that the shape is equal and all elements of the first object are strictly smaller than those of the second object. An exception is raised at shape mismatch or incorrectly ordered values. Shape mismatch does not raise if an object has zero dimension. In contrast to the standard usage in numpy, NaNs are compared, 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. Raises ------ AssertionError If actual and desired objects are not equal. See Also -------- assert_array_equal: tests objects for equality assert_array_almost_equal: test objects for equality up to precision Examples -------- >>> np.testing.assert_array_less([1.0, 1.0, np.nan], [1.1, 2.0, np.nan]) >>> np.testing.assert_array_less([1.0, 1.0, np.nan], [1, 2.0, np.nan]) Traceback (most recent call last): ... AssertionError: Arrays are not less-ordered Mismatched elements: 1 / 3 (33.3%) Max absolute difference: 1. Max relative difference: 0.5 x: array([ 1., 1., nan]) y: array([ 1., 2., nan]) >>> np.testing.assert_array_less([1.0, 4.0], 3) Traceback (most recent call last): ... AssertionError: Arrays are not less-ordered Mismatched elements: 1 / 2 (50%) Max absolute difference: 2. Max relative difference: 0.66666667 x: array([1., 4.]) y: array(3) >>> np.testing.assert_array_less([1.0, 2.0, 3.0], [4]) Traceback (most recent call last): ... AssertionError: Arrays are not less-ordered (shapes (3,), (1,) mismatch) x: array([1., 2., 3.]) y: array([4]) TzArrays are not less-orderedF)rr!rrN)r2r__lt__rr<r<r=rs L rcCst||dSr)exec)Zastrrr<r<r=r nsr c Csd}ddl}t|ts&ttt|t|ts@ttt|||krLdSt|| d| d}g}|rP| d}| drqp| drB|g}| d}| dr| || d}| dstt|| ||r| d} | dr| | n | d| |dd|ddkr6qp||qptt|qp|sZdSd d |} ||krt| dS) a 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: rE)difflibrLrrGrrMrDifferrrpop startswithrzinsertextendrrstrip) rrrIrdiffZ diff_listd1rtd2Zd3rCr<r<r=rrsP                  rc sddlm}ddl}|dur0td}|jd}tjtj |d}|||}| |}|j dd}g|rfdd } nd} |D]} |j | | d q|jdkr|rtd d dS) aV 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__Frcs |Sr)rz)srCr<r=rrzrundocs..)outzSome doctests failed: %sr)Znumpy.distutils.misc_utilrdoctestsys _getframe f_globalsosrcsplitextbasenameZ DocTestFinderrZ DocTestRunnerrunZfailuresrGr) filenameZraise_on_errorrr rsnamemtestsrunnerr testr<r r=rs"     rcGst}|jj|S)aDecorator to check for raised exceptions. The decorated test function must raise one of the passed exceptions to pass. If you want to test many assertions about exceptions in a single test, you may want to use `assert_raises` instead. .. warning:: This decorator is nose specific, do not use it if you are using a different test framework. Parameters ---------- args : exceptions The test passes if any of the passed exceptions is raised. Raises ------ AssertionError Examples -------- Usage:: @raises(TypeError, ValueError) def test_raises_type_error(): raise TypeError("This test passes") @raises(Exception) def test_that_fails_by_passing(): pass )rDZtoolsr)rrAr<r<r=rs"rc@seZdZddZdS)_DummycCsdSrr<)selfr<r<r=nopsz _Dummy.nopN)r8r9r:rr<r<r<r=rsrrcOsd}tj|i|S)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)rkwargsrIr<r<r=rsrcOsd}tj||g|Ri|S)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`. Notes ----- .. versionadded:: 1.9.0 T)rassertRaisesRegex)Zexception_classZexpected_regexprrrIr<r<r=r%5sr%c s|durtdtj}n t|}|j}ddlmfdd|D}|D]\}zt|drh|j }n|j }Wnt yYqPYn0| |rP| dsPt||||qPdS) 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 isfunctioncsg|]}|r|qSr<r<).0_mr r<r= jrz$decorate_methods..compat_func_name_)recompilersep__dict__inspectr!valueshasattrr%r8AttributeErrorsearchrsetattr)cls decoratorZ testmatchZcls_attrmethodsfunctionfuncnamer<r r=rJs       rr@c Csftd}|j|j}}t|d|dd}d}t}||krT|d7}t|||q6t|}d|S)aG 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 r@z Test name: rkrrg{Gz?)r r f_localsrr(rr) Zcode_strtimeslabelframelocsglobscoderelapsedr<r<r=r"ys!  r"c CstsdSddl}ddl}|ddd}|}d}|z@t|}tdD]}|||}qNt t||kW| n | 0~dS)zg Check that ufuncs don't mishandle refcount of object `1`. Used in a few regression tests. TrNi'rxr@) r0gcrr Zreshapedisabler r?rr#enable) opr?rbcrrcjdr<r<r=_assert_valid_refcounts   rHHz>c sfd}ddlfdd}||}}dddd} t|||t||| d dS) a Raises an AssertionError if two objects are not equal up to desired tolerance. 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)``. .. versionadded:: 1.5.0 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. Raises ------ AssertionError If actual and desired are not equal up to specified precision. See Also -------- assert_array_almost_equal_nulp, assert_array_max_ulp 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) TrNcsjjj||dS)N)rtolatolr)corenumericiscloserrKrrrJr<r=rsz assert_allclose..comparezNot equal to tolerance rtol=gz, atol=)rr!rr)rrr2r) rrrJrKrrr!rIrrr<rOr=r)s-r)c Csd}ddl}||}||}|||||k||}|||||ks||sh||rrd|}n|t||} d|| f}t|dS)a Compare two arrays relatively to their spacing. This is a relatively robust method to compare two arrays whose amplitude is variable. Parameters ---------- x, y : array_like Input arrays. nulp : int, optional The maximum number of unit in the last place for tolerance (see Notes). Default is 1. Returns ------- None Raises ------ AssertionError If the spacing between `x` and `y` for one or more elements is larger than `nulp`. See Also -------- assert_array_max_ulp : Check that all items of arrays differ in at most N Units in the Last Place. spacing : Return the distance between x and the nearest adjacent number. Notes ----- An assertion is raised if the following condition is not met:: abs(x - y) <= nulps * spacing(maximum(abs(x), abs(y))) Examples -------- >>> 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: X and Y are not equal to 1 ULP (max is 2) TrNzX and Y are not equal to %d ULPz+X and Y are not equal to %d ULP (max is %g)) rrspacingwhererrr nulp_diffrG) rOrZnulprIraxZayrefrCZmax_nulpr<r<r=r$s1    r$cCs@d}ddl}t|||}|||ks>> 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))rrSrrGr)rrCZmaxulprrIrretr<r<r=r&:s*  r&csddl|r*j||d}j||d}n|}|}||}|s^|rftdj|g|d}j|g|d}j||<j||<|j|jkst d|j|jffdd}t |}t |}||||S)anFor 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 rNrz'_nulp not implemented for complex arrayz+x and y do not have the same shape: %s - %scsj|||d}|SNr)rr)rxryvdtrrr<r=_diffsznulp_diff.._diff) rrZ common_typerrurrrJrr integer_repr)rOrrtr\rXrYr<r[r=rSns*       rScCsB||}|jdks.|||dk||dk<n|dkr>||}|S)Nr@r)viewr)rOrZcomprXr<r<r= _integer_reprs   racCs|ddl}|j|jkr(t||j|dS|j|jkrHt||j|dS|j|jkrht||j|dSt d|jdS)zQReturn the signed-magnitude interpretation of the binary representation of x.rNiilzUnsupported dtype ) rrfloat16raint16r int32float64int64r)rOrr<r<r=r]s   r]ccsld}tN}||}dVt|dksJ|dur:d|nd}td|Wdn1s^0YdS)NTr when calling rEzNo warning raised)r1recordrrG) warning_classrrIsuprtname_strr<r<r=_assert_warns_contexts  rlcOs`|s t|S|d}|dd}t||jd||i|WdS1sR0YdS)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. .. versionadded:: 1.4.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 rr@Nr)rlr8)rirrrr<r<r=r's - r'ccszd}tjddV}tddVt|dkrX|dur@d|nd}td|d|Wdn1sl0YdS) NTrhalwaysrrgrEz Got warningsr)warningscatch_warnings simplefilterrrG)rrIrtrkr<r<r=_assert_no_warnings_context s  rscOs\|s tS|d}|dd}t|jd||i|WdS1sN0YdS)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. .. versionadded:: 1.7.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`. rr@Nrm)rsr8rrrr<r<r=r(s  r(binaryc #sd}d}tdD]tdtd|D]|dkrtfdd}tfdd }|||d ffV|}|||d ffV|d d |d d |d d d ffV|d d |d d |d d d ffV|d d |d d |d d dffV|d d |d d |d d dffV|dkr.fdd}fdd} tfdd }||| |d ffV|}||| |dffV| }||||dffV|d d |d d | d d |d d d ffV|d d |d d | d d |d d d ffV|d d |d d | d d |d d d ffV|d d |d d | d d |d d dffV|d d |d d | d d |d d dffV|d d |d d | d d |d d dffVq.qd S)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, %srrZunarycstddSrWr r<rorr<r=rXrz%_gen_alignment_data..rNz out of placezin placer@r[aliasedrucstddSrWrwr<rxr<r=rfrcstddSrWrwr<rxr<r=rgrz in place1z in place2)rrr ) rrMmax_sizeZufmtZbfmtinpr rGZinp1Zinp2r<rxr=_gen_alignment_data:sn    $$$&&&r}c@seZdZdZdS)r*z/Ignoring this exception due to disabled featureNr7r<r<r<r=r*sr*c os4t|i|}z|VWt|n t|0dS)zContext manager to provide a temporary test folder. All arguments are passed as this to the underlying tempfile.mkdtemp function. N)rshutilrmtree)rrZtmpdirr<r<r=r.sr.c osBt|i|\}}t|z|VWt|n t|0dS)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)rrfdrcr<r<r=r-s  r-cs>eZdZdZdZd fdd ZfddZfdd ZZS) r+a< Context 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 r<Fcs*t||j|_i|_tj|ddS)Nrn)setunion class_modulesmodules_warnreg_copiessuper__init__)rrhr __class__r<r=rsz!clear_and_catch_warnings.__init__cs<|jD]*}t|dr|j}||j|<|qtSN__warningregistry__)rr-rcopyrclearr __enter__)rmodZmod_regrr<r=rs    z"clear_and_catch_warnings.__enter__csLtj||jD]4}t|dr*|j||jvr|j|j|qdSr)r__exit__rr-rrrupdate)rexc_inforrr<r=rs      z!clear_and_catch_warnings.__exit__)Fr<) r8r9r:r;rrrr __classcell__r<r<rr=r+s ) r+c@szeZdZdZdddZddZeddd fd d Zeddfd d ZeddfddZ ddZ ddZ ddddZ ddZ dS)r1a 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 rocCs&d|_g|_|dvrtd||_dS)NF>locationromoduleoncezunsupported forwarding rule.)_entered _suppressionsr_forwarding_rule)rZforwarding_ruler<r<r=r5s zsuppress_warnings.__init__cCs:ttdrtdS|jD]}t|dr|jqdS)N_filters_mutatedr)r-rpr _tmp_modulesrr)rrr<r<r=_clear_registries?s    z#suppress_warnings._clear_registriesrENFcCs|r g}nd}|jr|dur.tjd||dn8|jddd}tjd|||d|j|||j ||t |t j ||fn |j ||t |t j ||f|S)Nrocategorymessage.\.$rrr)rrpfilterwarningsr8replaceraddr_tmp_suppressionsrzr'r(Ir)rrrrrh module_regexr<r<r=_filterKs, zsuppress_warnings._filtercCs|j|||dddS)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. FrrrrhNrrrrrr<r<r=filterds zsuppress_warnings.filtercCs|j|||ddS)ai 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. Trrrr<r<r=rh{s zsuppress_warnings.recordcCs|jrtdtj|_tj|_|jddt_d|_g|_t|_ t|_ g|_ |j D]j\}}}}}|durv|dd=|durtj d||dqV|jddd}tj d|||d|j |qV|jt_||S) Nz%cannot enter suppress_warnings twice.Trorrrrr)r RuntimeErrorrp showwarning _orig_showfilters_filtersrrr _forwardedlogrrr8rr _showwarningr)rcatZmessr&rrrr<r<r=rs4 zsuppress_warnings.__enter__cGs*|jt_|jt_|d|_|`|`dS)NF)rrprrrrr)rrr<r<r=rs zsuppress_warnings.__exit__) use_warnmsgcOs|j|jdddD]\}} } } } t||r| |jddur| dur| dur~t||||fi|} |j| | | dS| j |r| durt||||fi|} |j| | | dSq|j dkr|dur|j ||||g|Ri|n | |dS|j dkr(|j|f}n4|j dkrB|j||f}n|j dkr\|j|||f}||j vrldS|j ||dur|j ||||g|Ri|n | |dS)Nr[rrorrr)rr issubclassmatchrrrrzrrrrZ _orig_showmsgrr)rrrrlinenorrrrr&patternrZrecrC signaturer<r<r=rs`                zsuppress_warnings._showwarningcstfdd}|S)z_ Function decorator to apply certain suppressions to a whole function. cs6|i|WdS1s(0YdSrr<)rrrrr<r=new_funcsz,suppress_warnings.__call__..new_funcr)rrrr<rr=__call__szsuppress_warnings.__call__)ro)r8r9r:r;rrWarningrrrhrrrrr<r<r<r=r1sI     3r1c csd}tsdVdStttt}zptdD]}tdkr8qVq8tdt tj dVt}tj dd}Wtj dd=t |t n tj dd=t |t 0|r|durd|nd}t d||t|ddd |DdS) NTrxrz]Unable to fully collect garbage - perhaps a __del__ method is creating more reference cycles?rgrEzXReference cycles were found{}: {} objects were collected, of which {} are shown below:{}c ss4|],}dt|jt|t|ddVqdS)z {} object with id={}: {}rz N)rarMr8idrpformatr)r"ryr<r<r= * s z/_assert_no_gc_cycles_context..)r0r#r? isenabledr@ get_debugrcollectr set_debugZ DEBUG_SAVEALLgarbagerArGrarr)rrIZgc_debugrZn_objects_in_cyclesZobjects_in_cyclesrkr<r<r=_assert_no_gc_cycles_context sH          rcOs\|s tS|d}|dd}t|jd||i|Wdn1sN0YdS)a3 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() .. versionadded:: 1.15.0 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. rr@Nrm)rr8rtr<r<r=r35 s  r3cCs0ttr,ttttdS)a1 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)r?rr/r<r<r<r=r4W s r4csddlfdd}|S)z:Decorator to skip a test if not enough memory is availablerNcstfdd}|S)NcsLt}|dur|z|i|WStyFdYn0dS)NzMemoryError raised)check_free_memoryskip MemoryErrorZxfail)rkwrC) free_bytesrpytestr<r=wrappern s  z3requires_memory..decorator..wrapperrrrrrrr=r2m s z"requires_memory..decorator)r)rr2r<rr=requires_memoryi src Csd}tj|}|durtz t|}Wn8ty\}z td|d|WYd}~n d}~00|dd|d}n0t}|durd}d }n|dd |dd }||kr|SdS) z Check whether `free_bytes` amount of memory is currently free. Returns: None if enough memory available, otherwise error message ZNPY_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.r[z GB memory required, but z GB available)renvironget _parse_sizer_get_mem_available)renv_varZ env_valueZmem_freerrCr<r<r=r s   *  rcCsdddddddddddddd d }td d |tj}||}|r`|d |vrpt d|dt t |d||d S)z3Convert memory size strings ('12 GB' etc.) to floatr@ii@Biʚ;lJ)ii@l)rErCrrrPr^kbmbgbtbZkibZmibZgibZtibz^\s*(\d+|\d+\.\d+)\s*({0})\s*$|rzvalue z not a valid size) r'r(rarkeysrrlowergrouprrpr)Zsize_strsuffixesZsize_rerr<r<r=r s rc Cszddl}|jWSttfy*Yn0tjdri}tddD}|D].}| }t |dd||d d <qLWdn1s0Yd |vr|d S|d |d SdS) z5Return available memory in bytes, or None if unknown.rNriz /proc/meminforjr@r:Z memavailableZmemfreecached) psutilZvirtual_memory availablerBr.r platformrrmrorpstripr)rinforslinepr<r<r=r s   Brcs*ttdsStfdd}|SdS)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 s>t}z$td|i|Wt|St|0dSr)r rsettrace)rrZoriginal_tracerr<r=r s  z_no_tracing..wrapperN)r-r rrr<rr= _no_tracing s  rc CsFztddd}Wn(ty@}zd}WYd}~n d}~00|S)NCS_GNU_LIBC_VERSIONrkr@0.0)rconfstrrsplitrq)verinstr<r<r=_get_glibc_version s rcCstdkot|kS)Nr) _glibcverrr<r<r=r rr)rE)Nr[NN)rer)r|Tr}r~)rET)rrET)rrET)rETrErTT)rET)rrET)rET)NT)N)r@N)rIrTrET)r@)r@N)N)N)N)N)nr;rr rr'r?rrp functoolsrrr~rtempfilerrZ unittest.caserrrrrrKrr r r r r rrZnumpy.linalg.lapack_liteior__all__rqr,ZKnownFailureTestr!python_implementationr/r-r6rr0ZlinalgZ lapack_liteZ_ilp64r5rDr#rQrWrYrrdrgetpidrrrrrrr2rrrr rrrZunittestZTestCaserrrr%rr"rHr)r$r&rSrar]contextmanagerrlr'rsr(r}r*r.r-rqr+r1rr3r4rrrrrrrZ_glibc_older_thanr<r<r<r=s  (            !) ~ c  S q SG .( / . : ? 4 ? 6 $E  B 3"