iѸ%SrSSKrSSKrSSKrSSKrSSKJrJrJr SSK J r J r J r SSK Jr SSKJrJrJrJrJr SSKJr SSKJr SS KJr SS KJrJr SS KJr SS K J!r! SS K"J#r# \(aSSK$J%r% S/r&\"S5r'/SQr(\)\*\+S'\ \"SS\ 555r,\ "SS\ 55r-"SS\ 5r.\ "SS\ \.S95r/"SS\R`5r1SSSSSSSSSSSSS. r2S \34S!jr4\#\S"S5r5S"\*S#\'S$\\6S \'4S%jr7S&\S#\6S"\*S \4S'jr8S(\9S \94S)jr:S*\S+S \S+4S,jr;S-\\-S \\-4S.jr\/S244S3jr?S4\9\@-\R`-S-S \1S-4S5jrAS6\*S \*4S7jrB"S8S9\C5rD"S:S\DS9rE\RS;\ES \\ESS44S<j5rG\E"S=S>\\,R\>"\-5S?S@SA\1"SBSC9S>SDS9 rI\ERSE\I5 \ERSE5 \ERce\E"S@SSS@\/R/SF9rM\ERSG\M5 \4"5(a\ERSG5 \ERce\N"\(5\R"\ER5RR5Vs1sH5nUR\RR:XdM)URiM7 sn:Xdegs snf)HzThe settings module configures runtime options for Hypothesis. Either an explicit settings object can be used or the default object on this module can be modified. N) Collection GeneratorSequence)EnumEnumMetaunique)total_ordering) TYPE_CHECKINGAnyClassVarOptionalTypeVarInvalidArgument)AVAILABLE_PROVIDERS)get_pretty_function_description) check_type try_convert)not_set)note_deprecation)DynamicVariableExampleDatabasesettingsT max_examples derandomizedatabase verbosityphasesstateful_step_countreport_multiple_bugssuppress_health_checkdeadline print_blobbackend all_settingsc^\rSrSrSrSrSrSrSr\ S5r S\ 4S jr \ S SS\4S j5rS \S\4U4S jjrS \S\4SjrSrU=r$) Verbosity?z=Options for the |settings.verbosity| argument to |@settings|.quietnormalverbosedebugc[U[5(a@[U[5(d+SSSSS.nX;a[SUSX!S3S S S S 9 U"X!5$g) Nr,r-r.r/)rzPassing Verbosity(zn) as an integer is deprecated. Hypothesis now treats Verbosity values as strings, not integers. Use Verbosity. instead. 2025-11-05Fr2since has_codemod stacklevel isinstanceintboolrclsvalue int_to_names S/var/www/html/ai-image-ml/venv/lib/python3.13/site-packages/hypothesis/_settings.py _missing_Verbosity._missing_ast eS ! !*UD*A*A%(yWMK# (0%%0%7$8 C' % ;-..returnc SUR3$)Nz Verbosity.nameselfs rB__repr__Verbosity.__repr__rsDII;''rEr@cv[RRS[RRS[RRS[R RS0n[ UR55[Vs/sHo"RPM sn:XdeXR$s snf)Nrr1r2r3)r*r,rIr-r.r/listkeys)r@mappingr s rB _int_valueVerbosity._int_valueus OO !    ! !1    " "A OO !  GLLN# 'R 9 'RRRRzz""(Ss B6otherc|>[U[5(a[TU] U5$[R U5U:H$N)r;r*super__eq__rR)rKrT __class__s rBrXVerbosity.__eq__s5 eY ' '7>%( (##D)U22rEc[RU5n[U[5(a[RU5OUnX#:$rV)r*rRr;)rKrTvalue1value2s rB__gt__Verbosity.__gt__s9%%d+0:5)0L0L%%e,RWrE)__name__ __module__ __qualname____firstlineno____doc__r,r-r.r/ classmethodrCstrrL staticmethodr<rRr r=rXr^__static_attributes__ __classcell__rYs@rBr*r*?sH EF G  E  (#( #+ ## # #3C3D3 CDrEr*cZ\rSrSrSrSrSrSrSrSr Sr \ S 5r S \ 4S jrS rg )Phasez:Options for the |settings.phases| argument to |@settings|.explicitreusegeneratetargetshrinkexplainc[U[5(aB[U[5(d-SSSSSSS.nX;a[SUS X!S 3S S S S9 U"X!5$g)Nrorprqrrrsrt)rr1r2r3zPassing Phase(zf) as an integer is deprecated. Hypothesis now treats Phase values as strings, not integers. Use Phase.r4r5Fr2r6r:r>s rBrCPhase._missing_s eS ! !*UD*A*A K# $UG,!!,!3 4I?' % ;-..rErFc SUR3$)NzPhase.rHrJs rBrLPhase.__repr__s {##rEr`N)rarbrcrdrerorprqrrrsrtrfrCrgrLrir`rErBrmrmskDH EHFFG.$#$rErmc(^\rSrSrU4SjrSrU=r$)HealthCheckMetac>^[R[R4m[U4Sj[TU]555$)Nc36># UHoT;dM Uv M g7frVr`).0x deprecateds rB +HealthCheckMeta.__iter__..sI1!j5HAA1  ) HealthCheck return_valuenot_a_test_methoditerrW__iter__)rKrrYs @rBrHealthCheckMeta.__iter__s2!.. 0M0MN Iuw/1IIIrEr`)rarbrcrdrrirjrks@rBr|r|sJJrEr|c\rSrSrSr\S5rS\4Sjr\S\ S4Sj5r Sr Sr S r S rS rS rS rSrSrSrg)ra A |HealthCheck| is proactively raised by Hypothesis when Hypothesis detects that your test has performance problems, which may result in less rigorous testing than you expect. For example, if your test takes a long time to generate inputs, or filters away too many inputs using |assume| or |filter|, Hypothesis will raise a corresponding health check. A health check is a proactive warning, not an error. We encourage suppressing health checks where you have evaluated they will not pose a problem, or where you have evaluated that fixing the underlying issue is not worthwhile. With the exception of |HealthCheck.function_scoped_fixture| and |HealthCheck.differing_executors|, all health checks warn about performance problems, not correctness errors. Disabling health checks ----------------------- Health checks can be disabled by |settings.suppress_health_check|. To suppress all health checks, you can pass ``suppress_health_check=list(HealthCheck)``. .. seealso:: See also the :doc:`/how-to/suppress-healthchecks` how-to. Correctness health checks ------------------------- Some health checks report potential correctness errors, rather than performance problems. * |HealthCheck.function_scoped_fixture| indicates that a function-scoped pytest fixture is used by an |@given| test. Many Hypothesis users expect function-scoped fixtures to reset once per input, but they actually reset once per test. We proactively raise |HealthCheck.function_scoped_fixture| to ensure you have considered this case. * |HealthCheck.differing_executors| indicates that the same |@given| test has been executed multiple times with multiple distinct executors. We recommend treating these particular health checks with more care, as suppressing them may result in an unsound test. c [U[5(aE[U[5(d0SSSSSSSSS S . nX;a[S US X!S 3SSSS9 U"X!5$g)Ndata_too_largefilter_too_muchtoo_slowrlarge_base_examplerfunction_scoped_fixturediffering_executors nested_given) r1r2r3rw zPassing HealthCheck(zr) as an integer is deprecated. Hypothesis now treats HealthCheck values as strings, not integers. Use HealthCheck.r4r5Fr2r6r:r>s rBrCHealthCheck._missing_s eS ! !*UD*A*A#$!'&,)" K# *5'2''2'9&:)E' % ;-..rErFcLURRSUR3$)N.)rYrarIrJs rBrLHealthCheck.__repr__s"..))*!DII;77rEc8[SSSSS9 [[5$)NzC`HealthCheck.all()` is deprecated; use `list(HealthCheck)` instead.z 2023-04-16Tr1r6)rrOrr?s rBallHealthCheck.alls%  Q  K  rErrrrrrrrrr`N)rarbrcrdrerfrCrgrLrOrrrrrrrrrrrir`rErBrrs)V48#8!D'!!&N(OH "LI- ,S8J"0 %"LrEr) metaclassc&\rSrSrSrS\4SjrSrg)durationi~z2A timedelta specifically measured in milliseconds.rFcjUR5S-nSU[U5:Xa [U5OU<S3$)Niztimedelta(milliseconds=)) total_secondsr<)rKmss rBrLduration.__repr__s5    !D ((B#b'MRr(LANNrEr`N)rarbrcrdrergrLrir`rErBrr~s<O#OrErtrue) CI&__TOX_ENVIRONMENT_VARIABLE_ORIGINAL_CITF_BUILDzbamboo.buildKey BUILDKITECIRCLECI CIRRUS_CICODEBUILD_BUILD_IDGITHUB_ACTIONS GITLAB_CIHEROKU_TEST_RUN_IDTEAMCITY_VERSIONrFcJ[S[R555$)Nc3# UHBupU[R;=(a! USL=(d [RUU:Hv MD g7frV)osenviron)rkeyr@s rBris_in_ci..s@*JC rzzIu}H 350HI*sA A )any_CI_VARSitemsr`rErBis_in_cirs# "..* rErIr@choicesc@X;aSUSU<SU<3n[U5eU$)NzInvalid , z. Valid choices: r)rIr@rmsgs rB_validate_choicesrs1 b ):7+Fc"" LrEr?c U"U5$![a+ [USUSSRSU5535Sef=f)N=z( is not a valid value. The options are: rc3L# UHn[UR5v M g7frV)reprrI)rms rBr'_validate_enum_value..s8Cqd166llCs"$) ValueErrorrjoin)r?r@rIs rB_validate_enum_valuers\5z fAeWII8C889 ;  s 5?rcP[[USS9 US:a[SU<S35eU$)NrrHr1z max_examples=zg must be at least one. If you want to disable generation entirely, use phases=[Phase.explicit] instead.rr<r)rs rB_validate_max_examplesrs?sL~6aL+,S S   rErrcNSSKJn Ub[X5(aU$[S5e)NrrzArguments to the database setting must be None or an instance of ExampleDatabase. Use one of the database classes in hypothesis.database)hypothesis.databaserr;r)rrs rB_validate_databasers.4:h@@   rEr!c^[[TS5m[ST55m[U4Sj[[555$)Nr!c3@# UHn[[USS9v M g7f)r!rHN)rrm)rphases rBr#_validate_phases..sGMeUE9vc36># UHoT;dM Uv M g7frVr`)rrr!s rBrrsCK5F?Kr)rtuplerOrm)r!s`rB_validate_phasesrs?  1F GMF CDKC CCrEr"cP[[USS9 US:a[SU<S35eU$)Nr"rHr1zstateful_step_count=z must be at least one.r)r"s rB_validate_stateful_step_countrs<s'.CDQ"#6"99O P   rE suppressions.c[[US5nUHCnU[R[R4;dM)[ SUR S3SSSS9 ME [SU55$) Nr$zThe z= health check is deprecated, because this is always an error.z 2023-03-15Fr2r6c3@# UHn[[USS9v M g7f)r$rHN)rr)r health_checks rBr2_validate_suppress_health_check..s!(L [,=TU(r)rrrrrrrI)rrs rB_validate_suppress_health_checkrsuul4KLL$ K44k6S6ST T |(())fg"!  % ( rEr%cUcU$[SU<S[U5RS35n[U[[ 45(a![U[ 5(aUe[US9n[U[R5(aAU[R"S5::a[SU<S35e[UR5S9$Ue![a [SU<S35Sef=f) Nz deadline=z (type zx) must be a timedelta object, an integer or float number of milliseconds, or None to disable the per-test-case deadline. millisecondszi is invalid, because it is too large to represent as a timedelta. Use deadline=None to disable deadlines.rzf is invalid, because it is impossible to meet a deadline <= 0. Use deadline=None to disable deadlines.)seconds) rtyperar;r<floatr=r OverflowErrordatetime timedeltar)r%invalid_deadline_errors rB_validate_deadliners , H'>&?@" " (S%L)) h % %( ( X6H (H..// x))!, ,!H<(II  6 6 899   !H<(JJ  s  C C&r'cU[;a:US:XaSn[SU<SU35e[SU<S[[5<35eU$)N crosshairz4`pip install "hypothesis[crosshair]"` and try again.zbackend=z is not available. zP is not available - maybe you need to install a plugin? Installed backends: )rrsorted)r'installs rB_validate_backendr sc)) k !LG!HWK7KG9"UV Vwk"))/0C)D(G I   NrEch^\rSrSrU4Sjr\S\S4Sj5rS\S\ SS4U4S jjr S r S r U=r $) settingsMetaic&>[TU]"U0UD6 grV)rW__init__)r?argskwargsrYs rBrsettingsMeta.__init__s $)&)rErFrc[RnUbU$[[SS5bI[Rce[R [R5 [Rce[R$)N_current_profile)default_variabler@getattrrr load_profile)r?vs rBdefaultsettingsMeta.defaultsk  " " =H 8/ 6 B,,8 88  ! !(";"; <#))5 55%%%rErIr@Nc>US:Xa [S5eURS5(d[SUSU<S35e[TU] X5 g)Nrz^Cannot assign to the property settings.default - consider using settings.load_profile instead._z"Cannot assign hypothesis.settings.rz - the settings class is immutable. You can change the global default settings with settings.load_profile, or use @settings(...) to decorate your test instead.)AttributeError startswithrW __setattr__)r?rIr@rYs rBrsettingsMeta.__setattr__'sc 9  @ %% 4TF!E9E11  D(rEcg)Nzhypothesis.settingsr`rs rBrLsettingsMeta.__repr__6s$rEr`)rarbrcrdrpropertyr rrgobjectrrLrirjrks@rBrrsL*&,&& )s )6 )d )%%rErcr^\rSrSr%Sr0r\\\S4\ S'Sr \\S-\ S'S1\ \ \ \ \ \ \ \ \ \ \ S. S\ SS\ S \S \ S S S S\SS\ S\S\SS\ \-\R$-S-S\S\SS4Sjjjr\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S 5r\S!5r\S"5r\S#5rS$\ S\ 4S%jr!S&\S'\"SS4U4S(jjr#S\4S)jr$S\4S*jr%\&S1S&\S\ SS+\'SS4S,jj5r(\&S&\SS4S-j5r)\&S&\SS4S.j5r*\&S\4S/j5r+S0r,U=r-$)2ri:a A settings object controls the following aspects of test behavior: |~settings.max_examples|, |~settings.derandomize|, |~settings.database|, |~settings.verbosity|, |~settings.phases|, |~settings.stateful_step_count|, |~settings.report_multiple_bugs|, |~settings.suppress_health_check|, |~settings.deadline|, |~settings.print_blob|, and |~settings.backend|. A settings object can be applied as a decorator to a test function, in which case that test function will use those settings. A test may only have one settings object applied to it. A settings object can also be passed to |settings.register_profile| or as a parent to another |settings|. Attribute inheritance --------------------- Settings objects are immutable once created. When a settings object is created, it uses the value specified for each attribute. Any attribute which is not specified will inherit from its value in the ``parent`` settings object. If ``parent`` is not passed, any attributes which are not specified will inherit from the current settings profile instead. For instance, ``settings(max_examples=10)`` will have a ``max_examples`` of ``10``, and the value of all other attributes will be equal to its value in the current settings profile. Changes made from activating a new settings profile with |settings.load_profile| will be reflected in settings objects created after the profile was loaded, but not in existing settings objects. .. _builtin-profiles: Built-in profiles ----------------- While you can register additional profiles with |settings.register_profile|, Hypothesis comes with two built-in profiles: ``default`` and ``ci``. By default, the ``default`` profile is active. If the ``CI`` environment variable is set to any value, the ``ci`` profile is active by default. Hypothesis also automatically detects various vendor-specific CI environment variables. The attributes of the currently active settings profile can be retrieved with ``settings()`` (so ``settings().max_examples`` is the currently active default for |settings.max_examples|). The settings attributes for the built-in profiles are as follows: .. code-block:: python default = settings.register_profile( "default", max_examples=100, derandomize=False, database=not_set, # see settings.database for default behavior verbosity=Verbosity.normal, phases=tuple(Phase), stateful_step_count=50, report_multiple_bugs=True, suppress_health_check=(), deadline=duration(milliseconds=200), print_blob=False, backend="hypothesis", ) ci = settings.register_profile( "ci", parent=default, derandomize=True, deadline=None, database=None, print_blob=True, suppress_health_check=[HealthCheck.too_slow], ) You can replace either of the built-in profiles with |settings.register_profile|: .. code-block:: python # run more examples in CI settings.register_profile( "ci", settings.get_profile("ci"), max_examples=1000, ) _profilesNrrparentrrrrr r*r!rmr"r#r$rr%r&r'rFc SUlUb[[US5 U[S4;aU[S4;a[ SU<S35eSnU=(d [R UlU[LaUR RO [U5Ul U[LaUR RO [SUSS/S9Ul U[La [U5nX@lSUlU[LaUR R O[#[$USS 9UlU[LaUR R(O [+U5UlU[LaUR R.O [1U5UlU[LaUR R4O [S USS/S9UlU [LaUR R8O [;U 5UlU [LaUR R>O [AU 5Ul!U [LaUR RDO [S U SS/S9Ul#U [LaUR RHO [KU 5Ul&SUlg) NTrFz`. If you are running more than 100k examples for a test, consider using our :ref:`integration for coverage-guided fuzzing ` - it really shines when given minutes or hours to run. The default max examples is ``100``. )rrJs rBrsettings.max_exampless2!!!rEcUR$)a  If True, seed Hypothesis' random number generator using a hash of the test function, so that every run will test the same set of examples until you update Hypothesis, Python, or the test function. This allows you to `check for regressions and look for bugs `__ using separate settings profiles - for example running quick deterministic tests on every commit, and a longer non-deterministic nightly testing run. The default is ``False``. If running on CI, the default is ``True`` instead. )rrJs rBrsettings.derandomize s   rEcSSKJn URc!UR[LdeU"[5$UR c:UR[LaURR O URUlUR $)a' An instance of |ExampleDatabase| that will be used to save examples to and load previous examples from. If not set, a |DirectoryBasedExampleDatabase| is created in the current working directory under ``.hypothesis/examples``. If this location is unusable, e.g. due to the lack of read or write permissions, Hypothesis will emit a warning and fall back to an |InMemoryExampleDatabase|. If ``None``, no storage will be used. See the :ref:`database documentation ` for a list of database classes, and how to define custom database classes. r) _db_for_path)rr&rrrrr)rKr&s rBrsettings.databasest 5 >> !>>W, ,,( (  (+/>>W+D''$..  !$$$rEcUR$)a Control the verbosity level of Hypothesis messages. To see what's going on while Hypothesis runs your tests, you can turn up the verbosity setting. .. code-block:: pycon >>> from hypothesis import settings, Verbosity >>> from hypothesis.strategies import lists, integers >>> @given(lists(integers())) ... @settings(verbosity=Verbosity.verbose) ... def f(x): ... assert not any(x) ... f() Trying example: [] Falsifying example: [-1198601713, -67, 116, -29578] Shrunk example to [-1198601713] Shrunk example to [-128] Shrunk example to [32] Shrunk example to [1] [1] The four levels are |Verbosity.quiet|, |Verbosity.normal|, |Verbosity.verbose|, and |Verbosity.debug|. |Verbosity.normal| is the default. For |Verbosity.quiet|, Hypothesis will not print anything out, not even the final falsifying example. |Verbosity.debug| is basically |Verbosity.verbose| but a bit more so. You probably don't want it. Verbosity can be passed either as a |Verbosity| enum value, or as the corresponding string value, or as the corresponding integer value. For example: .. code-block:: python # these three are equivalent settings(verbosity=Verbosity.verbose) settings(verbosity="verbose") If you are using :pypi:`pytest`, you may also need to :doc:`disable output capturing for passing tests ` to see verbose output as tests run. )rrJs rBr settings.verbosityDsZrEcUR$)a Control which phases should be run. Hypothesis divides tests into logically distinct phases. - |Phase.explicit|: Running explicit examples from |@example|. - |Phase.reuse|: Running examples from the database which previously failed. - |Phase.generate|: Generating new random examples. - |Phase.target|: Mutating examples for :ref:`targeted property-based testing `. Requires |Phase.generate|. - |Phase.shrink|: Shrinking failing examples. - |Phase.explain|: Attempting to explain why a failure occurred. Requires |Phase.shrink|. The phases argument accepts a collection with any subset of these. E.g. ``settings(phases=[Phase.generate, Phase.shrink])`` will generate new examples and shrink them, but will not run explicit examples or reuse previous failures, while ``settings(phases=[Phase.explicit])`` will only run explicit examples from |@example|. Phases can be passed either as a |Phase| enum value, or as the corresponding string value. For example: .. code-block:: python # these two are equivalent settings(phases=[Phase.explicit]) settings(phases=["explicit"]) Following the first failure, Hypothesis will (usually, depending on which |Phase| is enabled) track which lines of code are always run on failing but never on passing inputs. On 3.12+, this uses :mod:`sys.monitoring`, while 3.11 and earlier uses :func:`python:sys.settrace`. For python 3.11 and earlier, we therefore automatically disable the explain phase on PyPy, or if you are using :pypi:`coverage` or a debugger. If there are no clearly suspicious lines of code, :pep:`we refuse the temptation to guess <20>`. After shrinking to a minimal failing example, Hypothesis will try to find parts of the example -- e.g. separate args to |@given| -- which can vary freely without changing the result of that minimal failing example. If the automated experiments run without finding a passing variation, we leave a comment in the final report: .. code-block:: python test_x_divided_by_y( x=0, # or any other generated value y=0, ) Just remember that the *lack* of an explanation sometimes just means that Hypothesis couldn't efficiently find one, not that no explanation (or simpler failing example) exists. )rrJs rBr!settings.phasessst||rEcUR$)aJ The maximum number of times to call an additional |@rule| method in :ref:`stateful testing ` before we give up on finding a bug. Note that this setting is effectively multiplicative with max_examples, as each example will run for a maximum of ``stateful_step_count`` steps. The default stateful step count is ``50``. )rrJs rBr"settings.stateful_step_counts(((rEcUR$)aK Because Hypothesis runs the test many times, it can sometimes find multiple bugs in a single run. Reporting all of them at once is usually very useful, but replacing the exceptions can occasionally clash with debuggers. If disabled, only the exception with the smallest minimal example is raised. The default value is ``True``. )rrJs rBr#settings.report_multiple_bugss)))rEcUR$)a" Suppress the given |HealthCheck| exceptions. Those health checks will not be raised by Hypothesis. To suppress all health checks, you can pass ``suppress_health_check=list(HealthCheck)``. Health checks can be passed either as a |HealthCheck| enum value, or as the corresponding string value. For example: .. code-block:: python # these two are equivalent settings(suppress_health_check=[HealthCheck.filter_too_much]) settings(suppress_health_check=["filter_too_much"]) Health checks are proactive warnings, not correctness errors, so we encourage suppressing health checks where you have evaluated they will not pose a problem, or where you have evaluated that fixing the underlying issue is not worthwhile. .. seealso:: See also the :doc:`/how-to/suppress-healthchecks` how-to. )rrJs rBr$settings.suppress_health_checks2***rEcUR$)ay The maximum allowed duration of an individual test case, in milliseconds. You can pass an integer, float, or timedelta. If ``None``, the deadline is disabled entirely. We treat the deadline as a soft limit in some cases, where that would avoid flakiness due to timing variability. The default deadline is 200 milliseconds. If running on CI, the default is ``None`` instead. )rrJs rBr%settings.deadlines~~rEcUR$)z If set to ``True``, Hypothesis will print code for failing examples that can be used with |@reproduce_failure| to reproduce the failing example. The default value is ``False``. If running on CI, the default is ``True`` instead. )rrJs rBr&settings.print_blobsrEcUR$)z .. warning:: EXPERIMENTAL AND UNSTABLE - see :ref:`alternative-backends`. The importable name of a backend which Hypothesis should use to generate primitive types. We support heuristic-random, solver-based, and fuzzing-based backends. )rrJs rBr'settings.backends}}rEtestcUn[U5(d[SU<S35e[R"U5(a]SSKJn [ X#5(a<Sn[XS5(a [S5e[XS5 XRl U$[S 5e[US5(a*[U5n[US UR<S U<35eXl SUlU$) zMake the settings object (self) an attribute of the test. The settings are later discovered by looking them up on the test itself. zNsettings objects can be called as a decorator with @given, but decorated test=z is not callable.r)RuleBasedStateMachine%_hypothesis_internal_settings_appliedFzhApplying the @settings decorator twice would overwrite the first version; merge their arguments instead.Tzg@settings(...) can only be used as a decorator on functions, or on subclasses of RuleBasedStateMachine.zC has already been decorated with a settings object. Previous: z This: )callablerinspectisclasshypothesis.statefulr: issubclassrsetattrTestCaserhasattrr!_hypothesis_internal_use_settingsr;)rKr8_testr: attr_namedescrs rB__call__settings.__call__ s!'!%'8:  ??4 A%77C 4E22)# .*.' %L 5A B B4D9E!'""'"I"I!LM"X'  37/6:3 rErIr@c>URS5(dUR(d [S5e[TU]X5$)Nrzsettings objects are immutable)rrrrWr)rKrIr@rYs rBrsettings.__setattr__:s6s##D,?,? !AB Bw"4//rEcv^[U4Sj[55nSRSRU55$)Nc3~># UH2nUS:wd[[5S:dMUS[TU5<3v M4 g7f)r'r1rN)lenrr)rrIrKs rBr$settings.__repr__..@sB $ !S)<%=%A .tfAgdD), -$s==z settings({})r)rr(formatr)rKbitss` rBrLsettings.__repr__?s5 $   $$TYYt_55rEc/n[H;n[X5nU[[U5:wdM$URUSU<35 M= SR [ U[ S95$)Nrr)r)r(rrappendrrrN)rKrQrIr@s rB show_changedsettings.show_changedGsY DD'E.. tfAeY/0!yy#.//rErc [[US5 [R(aS[R (a>[R[R [R :wa [SSSS9 Ub U(dUO [ SSU0UD6[R U'[R U:Xa[RU5 gg) a Register a settings object as a settings profile, under the name ``name``. The ``parent`` and ``kwargs`` arguments to this method are as for |settings|. If a settings profile already exists under ``name``, it will be overwritten. Registering a profile with the same name as the currently active profile will cause those changes to take effect in the active profile immediately, and do not require reloading the profile. Registered settings profiles can be retrieved later by name with |settings.get_profile|. rIzCannot register a settings profile when the current settings differ from the current profile (usually due to an @settings decorator). Register profiles at module level instead.z 2025-11-15F)r7r8Nrr`) rrgrr@rrrrr)rIrrs rBregister_profilesettings.register_profileOs& 3f%  " ")) &&(*<*>> settings.load_profile("myprofile") >>> settings.get_current_profile_name() 'myprofile' )rrr`rErBget_current_profile_name!settings.get_current_profile_names"((444(((rE)rrrrrrrrrrrrrrrV).rarbrcrdrerr dictrg__annotations__rrr r<r=rrrrrr rrrr r!r"r#r$r%r&r'rrHr rrLrUrhr rXr\rrarirjrks@rBrr:sTl24IxS*_-.3-1hsTz*1(,\$$#07!(&-#*%,;Brs  ;;''$IJB09=3 , CL  d3i IIIX=$D=$=$@JhJ f$/ffROx!!O .2 "$#8J#78>Cx7GAc&33 ()    DZ.D8E?Dss & U;PSCS=T  !EkH...5! _!< s s %4%Df )f )R h9XtT-A#B   < 3 '   )W-i ###   &//0  $# :: $###  <   x00 1 < < C C E Evv""/// AFF Es (K$ K$