?gSSKJr SSKJr SSKJr SSKJr SSKrSSKJ r SSK r SSK r SSK J r SSKJr SS KJr SS KJr SS KJr SS KJr SS KJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKrSSKJr \(aSSK J!r! S2Sjr""SS5r#Sr$"SS\#5r%"SS\#5r&"SS \#5r'"S!S"\#5r("S#S$\(5r)S3S4S%jjr*S5S&jr+S6S'jr,S7S(jr-\"S)\.S*9r/\S+S,.S8S-jj5r0\S9S.j5r0S:S/jr0\Rb\0l1\"S0S1\\RdRf\/55r4g);) annotations) Collection)Sized)DecimalN)Complex) TracebackType)Any)Callable)cast)ContextManager)final)Mapping)overload)Pattern)Sequence)Tuple)Type) TYPE_CHECKING)TypeVar)fail)ndarrayc[U5nURSS5 /SQnUHWupn [US[U55US'[US[U 55US'[US[U 55US'MY S[U5SUS3S U3S U3/UV V V s/sH%upn U S US3S U S US3S U S US33PM' sn n n -n U $s sn n n f) Nr)IndexObtainedExpected)rrrz(comparison failed. Mismatched elements: z / :zMax absolute difference: zMax relative difference: 2 #L>2 ,8 +7 'Gx 1Yq\N" #3x)A,/?&@HQyYZ|nL\C]^+7  K   s,C cz\rSrSrSrSrSrSSSjjrSSjrSSjr SSjr S r Sr SS jr SS jrS rSS jrSrg) ApproxBase?zdProvide shared utilities for making approximate comparisons between numbers or sequences of numbers.NdcXSnXlX0lX lX@lUR 5 g)NT)r.absrelnan_ok _check_type)selfr.r9r8r:__tracebackhide__s r1__init__ApproxBase.__init__Gs(    c[eNNotImplementedErrorr<s r1__repr__ApproxBase.__repr__Os!!r@cSSU3SU3/$)Nzcomparison failedz Obtained: z Expected: )r< other_sides r1 _repr_compareApproxBase._repr_compareRs#  %   r@cL^[U4SjTRU555$)Nc3P># UHupUTRU5:Hv M g7frB_approx_scalar).0axr<s r1 $ApproxBase.__eq__..Zs' 4SDAA$$Q' '4Ss#&)all_yield_comparisonsr<actuals` r1__eq__ApproxBase.__eq__Ys( 484K4KF4S   r@cSn[S5e)NTzVapprox() is not supported in a boolean context. Did you mean: `assert a == approx(b)`?)AssertionError)r<r=s r1__bool__ApproxBase.__bool__^s  e  r@c X:X+$rBrIrXs r1__ne__ApproxBase.__ne__gs ##r@c[U[5(a)[XRURUR S9$[ XRURUR S9$)N)r9r8r:) isinstancer ApproxDecimalr9r8r: ApproxScalar)r<rSs r1rPApproxBase._approx_scalarjsE a ! ! dhht{{S SA88$++NNr@c[e)z_Yield all the pairs of numbers to be compared. This is used to implement the `__eq__` method. rCrXs r1rWApproxBase._yield_comparisonsos "!r@cg)zrFrKrZr^__hash__rarPrWr;__static_attributes__rIr@r1r4r4?sJ(O"   H$O "Kr@r4c^[U[[45(a[U5nU"U4SjU55$[ U5(aUVs/sHn[ TU5PM sn$T"U5$s snf)z=Recursively map a function over a sequence of arbitrary depthc3<># UHn[TU5v M g7frB)_recursive_sequence_map)rQxifs r1rT*_recursive_sequence_map..sC2/266s)rdr tupletype_is_sequence_liker)rrSseq_typers` r1rrsd!dE]##7CCCC 1  9:;2'2.;;t .get_value_from_nested_lists%ELr@z3Impossible to compare arrays with different shapes.zShapes:  and c38# UHn[U5v M g7frB)range)rQrs r1rT,ApproxNumpy._repr_compare..s(J>aq>s)rz list[Any]rztuple[Any, ...]rnr ) itertoolsmathr.shaperrPr_as_numpy_arraysizeinfproductr8r"appendrqr2)r<rJrrrnp_array_shapeapprox_side_as_seqother_side_as_arrayr&r(r)r'r, approx_value other_valueabs_diffr%s r1rKApproxNumpy._repr_compares " .=   ,,4   !5!5!7  .j9"... 66 6E>*%0C0I0I/JK  "]]//y y  &&(J>(JKE56HPL45HPK*|44{BC"<: #%#'88L#&|K@P5P#QL$$U+L$'  ' E ./BJK./AIJ  '   MM         s6F%c4>SSKnURU5(dURU5nURU5(d%UR UR R :wag[TU]!U5$![an[ SUS35UeSnAff=f)Nrzcannot compare 'z' to numpy.ndarrayF) numpyisscalarasarray Exception TypeErrorrr.superrZ)r<rYnpe __class__s r1rZApproxNumpy.__eq__s{{6"" VF+{{6""v||t}}7J7J'Jw~f%%  V"26(:L MNTUU VsA88 BBBc## SSKnURU5(aMURURR5H#nXRUR 54v M% gURURR5H4nXR 5URUR 54v M6 g7f)Nr)rrndindexr.ritem)r<rYrrs r1rWApproxNumpy._yield_comparisonss ;;v  ZZ 3 34mmA.335555ZZ 3 34inn& a(8(=(=(???5sCCrIrp)rJzndarray | list[Any]rnrrrs) rurvrwrxryrFrKrZrWr} __classcell__rs@r1rrs"R+ > @& @ @r@rcT^\rSrSrSrS SjrS SjrS U4SjjrSrS Sjr Sr U=r $) ApproxMappingzuPerform approximate comparisons where the expected value is a mapping with numeric values (the keys can be anything).c SURR5VVs0sHupXRU5_M snn<S3$s snnfr)r.itemsrP)r<kvs r1rFApproxMapping.__repr__sDATATAVWAV111!44AVW[[\]]WsAc <SSKnURR5VVs0sHup4X0RU5_M nnn[ U5nUR *nUR *n/n [ UR5UR55Huupn X:wdMU RbsU bp[U[U RU - 55nU RS:Xa UR nO0[U[U RU - U R- 55nU RU 5 M U V s/sH'n [U 5[X5[X]54PM) nn [URUUU UU5$s snnf![a Nuf=fs sn f)Nrr)rr.rrPr#rzipvaluesr"r8ZeroDivisionErrorrrqr2)r<rJrrrapprox_side_as_mapr&r(r)r' approx_keyrrkeyr%s r1rKApproxMapping._repr_compares37--2E2E2G 2G$!A""1% %2G  !!34y y  7:  $ $ & (9(9(;8 3 &Z *((49P'*(#l.C.Ck.Q*R( (00C7+/88L+. , #%1%:%:[%H&2&;&;%<!",L$$Z0+8 2% $Xs:?+S1C1H-I J$   MM        I 6- s#F1>F 0/F 9.F FFc>[UR55[URR55:wag[TU]U5$![a gf=fNF)setkeysr.AttributeErrorrrZr<rYrs r1rZApproxMapping.__eq__)sZ 6;;=!S););)=%>>? w~f%%  s>A AAc#x# URR5HnXURU4v M g7frB)r.r)r<rYrs r1rW ApproxMapping._yield_comparisons2s2##%A)T]]1-- -&s8:c  SnURR5Hdup#[U[UR55(dM+Sn[ UR X#[ R"UR555e g)NTz[pytest.approx() does not support nested dictionaries: key={!r} value={!r} full mapping={})r.rrdrrformatpprintpformat)r<r=rrmsgs r1r;ApproxMapping._check_type6s_ ----/JC%dmm!455t 3v~~dmm7T UVV0r@rIrp)rJzMapping[object, float]rnrrrsrt rurvrwrxryrFrKrZrWr;r}rrs@r1rrs*7^. `&.WWr@rcT^\rSrSrSrS SjrS SjrS U4SjjrSrS Sjr Sr U=r $) ApproxSequenceLikei>zRPerform approximate comparisons where the expected value is a sequence of numbers.c^[TR5nU[[4;a[nSU"U4SjTR55<S3$)Nrc3F># UHnTRU5v M g7frBrO)rQrSr<s r1rT.ApproxSequenceLike.__repr__..Es!P-Q$"5"5a"8"8-!r)rr.rr )r<rs` r1rFApproxSequenceLike.__repr__AsB & E4= (H!P$--!PPSSTUUr@c SSKn[UR5[U5:wa&SS[UR5S[U53/$[URUR5n[U5nUR *nUR *n/n[ [X155HmunupX:wdM[U RU - 5n [X[5nU S:Xa UR nO[Xk[U 5- 5nURU5 Mo UVs/sH'n[U5[X5[X854PM) n n[URU UUUU5$s snf)Nrz1Impossible to compare lists with different sizes.z Lengths: rr) rr#r.rrPr enumeraterr8r"rrqr2) r<rJrrr&r(r)r'rrrrr%s r1rK ApproxSequenceLike._repr_compareGsg t}} Z 0CC ./uS_4EF  5T5H5H$--X !34y y  .7 " // *A* *|44{BC"<: #%#'88L#&|K@P5P#QL$$Q'/ # "VS'-?-B)C D"   MM         s.E'c>[U5[UR5:wag[TU]U5$![a gf=fr)r#r.rrrZrs r1rZApproxSequenceLike.__eq__psJ 6{c$--001w~f%%  s"6 AAc,[XR5$rB)rr.rXs r1rW%ApproxSequenceLike._yield_comparisonsxs6==))r@c Sn[UR5Hdup#[U[UR55(dM+Sn[ UR X2[ R"UR555e g)NTz]pytest.approx() does not support nested data structures: {!r} at index {} full sequence: {})rr.rdrrrrr)r<r=r,rSrs r1r;ApproxSequenceLike._check_type{s[ !$--0HE!T$--011v 1V^^DMM5R STT1r@rIrp)rJzSequence[float]rnrrrsrtrrs@r1rr>s(\V ' R&*UUr@rc^\rSrSr%SrSrS\S'SrS\S'S SjrSS jr S r \ S 5r S r g )rfizLPerform approximate comparisons where the expected value is a single number.g-q=zfloat | DecimalDEFAULT_ABSOLUTE_TOLERANCEgư>DEFAULT_RELATIVE_TOLERANCEc~[UR[5(dt[UR[[45(aO[ R "[UR5=(d [UR[55(a[UR5$URSn[UR[5(aEURR(a*[ R "UR5(dUS- nURSU3$![a SnNf=f)uReturn a string communicating both the expected value and the tolerance for the comparison being made. For example, ``1.0 ± 1e-6``, ``(3+4j) ± 5e-6 ∠ ±180°``. z.1eu ∠ ±180°z???u ± ) rdr.rmrrrisinfr8rq toleranceimag ValueError)r<vetted_tolerances r1rFApproxScalar.__repr__s t}}d + +t}}w.@AAzz#dmm,O 4==$0OPPt}}% % %"&..!5 4=='22MM&& 4>>22 N2 --%5$677 %$  %s*A2D-- D<;D<c^[U5nUb[U4SjUR55$[TR[ 5(a[U[ 5(dgUTR:Xag[TR[ 5(d@[TR[ [45(a[U[ [45(dg[R"[TR55(a2TR=(a [R"[U55$[R"[TR55(ag[TRU- 5TR:*nU$)zaReturn whether the given value is equal to the expected value within the pre-specified tolerance.c3F># UHnTRU5v M g7frB)rZ)rQrRr<s r1rT&ApproxScalar.__eq__..s<|!t{{1~~|rFT)rrVflatrdr.rmrrrisnanr8r:rr)r<rYrresults` r1rZApproxScalar.__eq__s"&)  .set_defaults 1 27 2r@rz&absolute tolerance can't be negative: z absolute tolerance can't be NaN.z&relative tolerance can't be negative: z relative tolerance can't be NaN.) r8rrrrr9rr.r")r<rabsolute_tolerancerelative_tolerances r1rApproxScalar.tolerances 3 )43R3RS  !89K8LM  ::( ) )?@ @ 88 xx#))) HHd55    !89K8LM  ::( ) )?@ @%::r@rIrprs)rurvrwrxryr__annotations__rrFrZr|propertyrr}rIr@r1rfrfsAV3872668>*ZH ,;,;r@rfc8\rSrSrSr\"S5r\"S5rSrg)rei zFPerform approximate comparisons where the expected value is a Decimal.z1e-12z1e-6rIN) rurvrwrxryrrrr}rIr@r1rere sP!(!1!(r@recSn[U[5(a[nO[U[5(a[nO[ U5(a[ U5n[nO^[U5(a[nOG[U[5(a,[U[[45(dSU<3n[U5e[nU"XX#5$)aAssert that two numbers (or two ordered sequences of numbers) are equal to each other within some tolerance. Due to the :doc:`python:tutorial/floatingpoint`, numbers that we would intuitively expect to be equal are not always so:: >>> 0.1 + 0.2 == 0.3 False This problem is commonly encountered when writing tests, e.g. when making sure that floating-point values are what you expect them to be. One way to deal with this problem is to assert that two floating-point numbers are equal to within some appropriate tolerance:: >>> abs((0.1 + 0.2) - 0.3) < 1e-6 True However, comparisons like this are tedious to write and difficult to understand. Furthermore, absolute comparisons like the one above are usually discouraged because there's no tolerance that works well for all situations. ``1e-6`` is good for numbers around ``1``, but too small for very big numbers and too big for very small ones. It's better to express the tolerance as a fraction of the expected value, but relative comparisons like that are even more difficult to write correctly and concisely. The ``approx`` class performs floating-point comparisons using a syntax that's as intuitive as possible:: >>> from pytest import approx >>> 0.1 + 0.2 == approx(0.3) True The same syntax also works for ordered sequences of numbers:: >>> (0.1 + 0.2, 0.2 + 0.4) == approx((0.3, 0.6)) True ``numpy`` arrays:: >>> import numpy as np # doctest: +SKIP >>> np.array([0.1, 0.2]) + np.array([0.2, 0.4]) == approx(np.array([0.3, 0.6])) # doctest: +SKIP True And for a ``numpy`` array against a scalar:: >>> import numpy as np # doctest: +SKIP >>> np.array([0.1, 0.2]) + np.array([0.2, 0.1]) == approx(0.3) # doctest: +SKIP True Only ordered sequences are supported, because ``approx`` needs to infer the relative position of the sequences without ambiguity. This means ``sets`` and other unordered sequences are not supported. Finally, dictionary *values* can also be compared:: >>> {'a': 0.1 + 0.2, 'b': 0.2 + 0.4} == approx({'a': 0.3, 'b': 0.6}) True The comparison will be true if both mappings have the same keys and their respective values match the expected tolerances. **Tolerances** By default, ``approx`` considers numbers within a relative tolerance of ``1e-6`` (i.e. one part in a million) of its expected value to be equal. This treatment would lead to surprising results if the expected value was ``0.0``, because nothing but ``0.0`` itself is relatively close to ``0.0``. To handle this case less surprisingly, ``approx`` also considers numbers within an absolute tolerance of ``1e-12`` of its expected value to be equal. Infinity and NaN are special cases. Infinity is only considered equal to itself, regardless of the relative tolerance. NaN is not considered equal to anything by default, but you can make it be equal to itself by setting the ``nan_ok`` argument to True. (This is meant to facilitate comparing arrays that use NaN to mean "no data".) Both the relative and absolute tolerances can be changed by passing arguments to the ``approx`` constructor:: >>> 1.0001 == approx(1) False >>> 1.0001 == approx(1, rel=1e-3) True >>> 1.0001 == approx(1, abs=1e-3) True If you specify ``abs`` but not ``rel``, the comparison will not consider the relative tolerance at all. In other words, two numbers that are within the default relative tolerance of ``1e-6`` will still be considered unequal if they exceed the specified absolute tolerance. If you specify both ``abs`` and ``rel``, the numbers will be considered equal if either tolerance is met:: >>> 1 + 1e-8 == approx(1) True >>> 1 + 1e-8 == approx(1, abs=1e-12) False >>> 1 + 1e-8 == approx(1, rel=1e-6, abs=1e-12) True You can also use ``approx`` to compare nonnumeric types, or dicts and sequences containing nonnumeric types, in which case it falls back to strict equality. This can be useful for comparing dicts and sequences that can contain optional values:: >>> {"required": 1.0000005, "optional": None} == approx({"required": 1, "optional": None}) True >>> [None, 1.0000005] == approx([None,1]) True >>> ["foo", 1.0000005] == approx([None,1]) False If you're thinking about using ``approx``, then you might want to know how it compares to other good ways of comparing floating-point numbers. All of these algorithms are based on relative and absolute tolerances and should agree for the most part, but they do have meaningful differences: - ``math.isclose(a, b, rel_tol=1e-9, abs_tol=0.0)``: True if the relative tolerance is met w.r.t. either ``a`` or ``b`` or if the absolute tolerance is met. Because the relative tolerance is calculated w.r.t. both ``a`` and ``b``, this test is symmetric (i.e. neither ``a`` nor ``b`` is a "reference value"). You have to specify an absolute tolerance if you want to compare to ``0.0`` because there is no tolerance by default. More information: :py:func:`math.isclose`. - ``numpy.isclose(a, b, rtol=1e-5, atol=1e-8)``: True if the difference between ``a`` and ``b`` is less that the sum of the relative tolerance w.r.t. ``b`` and the absolute tolerance. Because the relative tolerance is only calculated w.r.t. ``b``, this test is asymmetric and you can think of ``b`` as the reference value. Support for comparing sequences is provided by :py:func:`numpy.allclose`. More information: :std:doc:`numpy:reference/generated/numpy.isclose`. - ``unittest.TestCase.assertAlmostEqual(a, b)``: True if ``a`` and ``b`` are within an absolute tolerance of ``1e-7``. No relative tolerance is considered , so this function is not appropriate for very large or very small numbers. Also, it's only available in subclasses of ``unittest.TestCase`` and it's ugly because it doesn't follow PEP8. More information: :py:meth:`unittest.TestCase.assertAlmostEqual`. - ``a == pytest.approx(b, rel=1e-6, abs=1e-12)``: True if the relative tolerance is met w.r.t. ``b`` or if the absolute tolerance is met. Because the relative tolerance is only calculated w.r.t. ``b``, this test is asymmetric and you can think of ``b`` as the reference value. In the special case that you explicitly specify an absolute tolerance but not a relative tolerance, only the absolute tolerance is considered. .. note:: ``approx`` can handle numpy arrays, but we recommend the specialised test helpers in :std:doc:`numpy:reference/routines.testing` if you need support for comparisons, NaNs, or ULP-based tolerances. To match strings using regex, you can use `Matches `_ from the `re_assert package `_. .. warning:: .. versionchanged:: 3.2 In order to avoid inconsistent behavior, :py:exc:`TypeError` is raised for ``>``, ``>=``, ``<`` and ``<=`` comparisons. The example below illustrates the problem:: assert approx(0.1) > 0.1 + 1e-10 # calls approx(0.1).__gt__(0.1 + 1e-10) assert 0.1 + 1e-10 > approx(0.1) # calls approx(0.1).__lt__(0.1 + 1e-10) In the second example one expects ``approx(0.1).__le__(0.1 + 1e-10)`` to be called. But instead, ``approx(0.1).__lt__(0.1 + 1e-10)`` is used to comparison. This is because the call hierarchy of rich comparisons follows a fixed behavior. More information: :py:meth:`object.__ge__` .. versionchanged:: 3.7.1 ``approx`` raises ``TypeError`` when it encounters a dict value or sequence element of nonnumeric type. .. versionchanged:: 6.1.0 ``approx`` falls back to strict equality for nonnumeric types instead of raising ``TypeError``. Tz:pytest.approx() only supports ordered sequences, but got: )rdrrerr_is_numpy_arrayrrrrrrqbytesrrf)r.r9r8r:r=clsrs r1approxrsJ(G$$ - Hg & &  " ""8, 8 $ $  Hj ) )*XU|2T2TJ8,Wn xc **r@c[US5=(a2 [U[5=(a [U[[45(+$)N __getitem__)hasattrrdrrqr )r.s r1rrs6-( 3 x ' 38c5\2 2r@c[U5SL$)zf Return true if the given object is implicitly convertible to ndarray, and numpy is already imported. N)r)objs r1r r s 3 t ++r@cSSKnURRS5nUbfURU5(ag[ XR 5(aU$[ US5(d[ SS5(aURU5$g)z| Return an ndarray if the given object is implicitly convertible to ndarray, and numpy is already imported, otherwise None. rNr __array__r__array_interface__)sysmodulesgetrrdrrr)rrrs r1rrso kkoog&B ~ ;;s   ZZ ( (J S+ & &'%9N*O*O::c? " r@E)bound.)matchcgrBrI)expected_exceptionrs r1raisesr s r@cgrBrI)rfuncargskwargss r1r r s &)r@c<SnU(d[SU<S35e[U[5(aU4nOUnUHn[U[5(a[U[5(aM/Sn[U[5(a UR O[U5R n[ URU55e SU3nU(dTURSS5n U(a/SnUS R[U55- nUS - n[ U5e[XU 5$US n [U 5(d[ U <S [U 5S 35eU "USS0UD6 [#U5 g!Ua3n [RRR!U 5sSn A $Sn A ff=f)a\Assert that a code block/function call raises an exception type, or one of its subclasses. :param expected_exception: The expected exception type, or a tuple if one of multiple possible exception types are expected. Note that subclasses of the passed exceptions will also match. :kwparam str | re.Pattern[str] | None match: If specified, a string containing a regular expression, or a regular expression object, that is tested against the string representation of the exception and its :pep:`678` `__notes__` using :func:`re.search`. To match a literal string that may contain :ref:`special characters `, the pattern can first be escaped with :func:`re.escape`. (This is only used when ``pytest.raises`` is used as a context manager, and passed through to the function otherwise. When using ``pytest.raises`` as a function, you can use: ``pytest.raises(Exc, func, match="passed on").match("my pattern")``.) Use ``pytest.raises`` as a context manager, which will capture the exception of the given type, or any of its subclasses:: >>> import pytest >>> with pytest.raises(ZeroDivisionError): ... 1/0 If the code block does not raise the expected exception (:class:`ZeroDivisionError` in the example above), or no exception at all, the check will fail instead. You can also use the keyword argument ``match`` to assert that the exception matches a text or regex:: >>> with pytest.raises(ValueError, match='must be 0 or None'): ... raise ValueError("value must be 0 or None") >>> with pytest.raises(ValueError, match=r'must be \d+$'): ... raise ValueError("value must be 42") The ``match`` argument searches the formatted exception string, which includes any `PEP-678 `__ ``__notes__``: >>> with pytest.raises(ValueError, match=r"had a note added"): # doctest: +SKIP ... e = ValueError("value must be 42") ... e.add_note("had a note added") ... raise e The context manager produces an :class:`ExceptionInfo` object which can be used to inspect the details of the captured exception:: >>> with pytest.raises(ValueError) as exc_info: ... raise ValueError("value must be 42") >>> assert exc_info.type is ValueError >>> assert exc_info.value.args[0] == "value must be 42" .. warning:: Given that ``pytest.raises`` matches subclasses, be wary of using it to match :class:`Exception` like this:: with pytest.raises(Exception): # Careful, this will catch ANY exception raised. some_function() Because :class:`Exception` is the base class of almost all exceptions, it is easy for this to hide real bugs, where the user wrote this expecting a specific exception, but some other exception is being raised due to a bug introduced during a refactoring. Avoid using ``pytest.raises`` to catch :class:`Exception` unless certain that you really want to catch **any** exception raised. .. note:: When using ``pytest.raises`` as a context manager, it's worthwhile to note that normal context manager rules apply and that the exception raised *must* be the final line in the scope of the context manager. Lines of code after that, within the scope of the context manager will not be executed. For example:: >>> value = 15 >>> with pytest.raises(ValueError) as exc_info: ... if value > 10: ... raise ValueError("value must be <= 10") ... assert exc_info.type is ValueError # This will not execute. Instead, the following approach must be taken (note the difference in scope):: >>> with pytest.raises(ValueError) as exc_info: ... if value > 10: ... raise ValueError("value must be <= 10") ... >>> assert exc_info.type is ValueError **Using with** ``pytest.mark.parametrize`` When using :ref:`pytest.mark.parametrize ref` it is possible to parametrize tests such that some runs raise an exception and others do not. See :ref:`parametrizing_conditional_raising` for an example. .. seealso:: :ref:`assertraises` for more examples and detailed discussion. **Legacy form** It is possible to specify a callable by passing a to-be-called lambda:: >>> raises(ZeroDivisionError, lambda: 1/0) or you can specify an arbitrary callable with arguments:: >>> def f(x): return 1/x ... >>> raises(ZeroDivisionError, f, 0) >>> raises(ZeroDivisionError, f, x=0) The form above is fully supported but discouraged for new code because the context manager form is regarded as more readable and less error-prone. .. note:: Similar to caught exception objects in Python, explicitly clearing local references to returned ``ExceptionInfo`` objects can help the Python interpreter speed up its garbage collection. Clearing those references breaks a reference cycle (``ExceptionInfo`` --> caught exception --> frame stack raising the exception --> current frame stack --> local variables --> ``ExceptionInfo``) which makes Python keep all objects referenced from that cycle (including all local variables in the current frame) alive until the next cyclic garbage collection run. More detailed information can be found in the official Python documentation for :ref:`the try statement `. TzCExpected an exception type or a tuple of exception types, but got `z`. Raising exceptions is already understood as failing the test, so you don't need any special code to say 'this should never raise an exception'.z7expected exception must be a BaseException type, not {}zDID NOT RAISE rNz6Unexpected keyword arguments passed to pytest.raises: z, z" Use context-manager form instead?rz object (type: z) must be callabler)rrdr issubclass BaseExceptionrurrpopjoinsorted RaisesContextcallable_pytest_code ExceptionInfofrom_exceptionr) rr#r$r=expected_exceptionsexcrnot_amessagerr"rs r1r r "sZ QRdQghN O  $d++4F3H0"#t$$JsM,J,JKC$.sD$9$9CLLtCy?Q?QECJJu-. . # 123G +1::gt+D JC 499VF^, ,C 8 8CC. /%@@Aw~~thod4j\ASTU U A $qr( %f % M" A==..==a@ @ As E""F((FFFcV\rSrSrSSSjjrS SjrS SjrSrg) r+iNcXlX lX0lSUlURb6Sn[R "UR5 Ub[SU35 ggg![R a nUnSnAN/SnAff=f)Nz+Invalid regex pattern provided to 'match': )rr4 match_exprexcinforecompileerrorr)r<rr4r7re_errorrs r1r>RaisesContext.__init__s| #5 $>B ?? &H  4??+#B8*MN$ '88  s AA>2A99A>ct[RRR5UlUR$rB)r-r.r/ for_laterr8rEs r1 __enter__RaisesContext.__enter__s&}}22<<> ||r@c|SnUc[UR5 URce[XR5(dg[ [ [[[[4XU45nURRU5 URb%URRUR5 g)NTF) rr4r8r&rr rrrr fill_unfilledr7r)r<exc_typeexc_valexc_tbr=exc_infos r1__exit__RaisesContext.__exit__s !    ||'''($;$;<<d1gq-788f:UV ""8, ?? & LL  t /r@)r8rr7r4rB)rtype[E] | tuple[type[E], ...]r4rqr7str | Pattern[str] | Nonernro)rn_pytest._code.ExceptionInfo[E])rDztype[BaseException] | NonerEzBaseException | NonerFzTracebackType | Nonernrm)rurvrwrxr>r@rHr}rIr@r1r+r+sg 15 O9OO. O  O&,&%   r@r+)r$objectr%zSequence[tuple[str, str, str]]r&intr'zSequence[object]r(floatr)rOrnrrrl)r:rmrnr4)r.rMrnrm)rrMrnrm)rrMrnzndarray | None)rrJrrKrnzRaisesContext[E]) rrJr"zCallable[..., Any]r#r r$r rnrL)rrJr#r r$r rnz1RaisesContext[E] | _pytest._code.ExceptionInfo[E])5 __future__rcollections.abcrrdecimalrrnumbersrrr9typesrtypingr r r r r rrrrrrrr _pytest._coder-_pytest.outcomesrrrr2r4rrrrrfrerrr rr'rr rr.r/r+rIr@r1rXs"&!  ! !0$     :8K8K@e@*e@PIWJIWXBUBUJC;:C;L1L1V+r,* C}% (+5 %   )5) ) ) ) $ ) )q5q>AqMPq6qj>>)N7==#>#>q#AB))r@