+ 4ja0t$Rt^RIHt^RIt^RIHt^RIHt^RI H t ]'d^RI H t ^RI H t^RIHtR tR t]R ]R /t]P'4Uu/uF q]!4bK uptR ]R&]P.!RRP1]P'44,R,4tRRlt!RR]4tRRltRRltR#uupi)adConflict-kind constants and PEP 508 marker-variable mapping. A leaf module that :mod:`nab_python.config`, :mod:`nab_python.target`, and :mod:`nab_python._lockfile.disjointness` can import without forming a cycle. :class:`nab_python.config.ConflictKind` takes its enum values from ``KIND_EXTRA`` / ``KIND_GROUP`` so a rename here flows to every consumer. ) annotationsN) TYPE_CHECKING)UndefinedComparison) MarkerSet)Mapping)Set)Markerextragroupextrasdependency_groupszdict[str, frozenset[str]]EMPTY_MEMBERSHIP_SETSz\b(|z)\bc V^8dQhRRRR/#) marker_textstrreturnz str | None)formats"k/home/user/pdf2html-billing-ledger-validate/.venv/lib/python3.14/site-packages/nab_python/_conflict_kind.py __annotate__r2s--#-*-cb\PV4pV'dVP^4#R#)aReturn the lockfile-only set variable a marker tests, or ``None``. A dependency marker that tests ``extras`` or ``dependency_groups`` is a mistake (usually meant as ``extra ==``): those variables are defined only when consuming a lockfile, so they are empty at resolve time. N)_MEMBERSHIP_SET_PATTERNsearchr )rmatchs& rmembership_set_in_markerr2s) $ * *; 7E"5;;q>,,rc]tRt^=tRtRtR#)UnevaluableMarkerErroraA dependency marker parses but no comparison decides it. PEP 508 accepts any operator between a variable and a literal, and PEP 440 gives the compatible-release operator a meaning only over a release with at least two components. So ``python_full_version ~= "3"`` is a valid marker with nothing to evaluate, and ``sys_platform ~= "linux"`` is one on a variable that holds no version at all. A requirement the project declares is neither activated nor dropped by such a marker, and either guess changes what gets locked, so the run stops and names it. A candidate's own metadata takes the other route: ``Provider.get_dependencies`` already turns metadata it cannot read into a candidate skip. rN)__name__ __module__ __qualname____firstlineno____doc____static_attributes__rrrrr=s rrc V^8dQhRRRR/#)rmarkerrrrr)rs"rrrNs 3 3v 3) 3rc~\P!V4# \dpRT RT 2p\T4ThRp?ii;i)a4Return the algebra form of ``marker``. Each clause is checked against its operator while the set is built, so this is the one place a marker with no meaning can be caught. Raises :class:`UnevaluableMarkerError` naming the whole marker, since the failing clause alone does not say which dependency to edit. zmarker z cannot be evaluated: N)r from_markerrr)r'excmsgs& r marker_setr,NsH3$$V,, 3x5cU;$S)s23s <7<c$V^8dQhRRRRRR/#)rr'r environmentz$Mapping[str, str | AbstractSet[str]]rboolr)rs"rrr]s$,, ,!E, ,rcR\4/pVPV4VP\4\V4P V4#)apEvaluate a dependency marker for a resolve-time ``environment``. ``extra`` is set-valued: bound to the active extra names, ``extra == "x"`` tests membership and ``extra != "x"`` non-membership, both PEP 685 normalised. It defaults to the empty set when ``environment`` omits it. A standard variable a marker names but ``environment`` omits raises ``UndefinedEnvironmentName``; callers pass a complete ``ResolveTarget.marker_env``. The lockfile-only set variables are seeded empty, so a marker that tests one evaluates to False rather than raising. A clause no comparison decides raises :class:`UnevaluableMarkerError`. r ) frozensetupdater r,evaluate)r'r.envs&& rdependency_marker_holdsr5]s? /6y{-CCJJ{JJ$% f  & &s ++r)__conditional_annotations__r$ __future__rretypingr_vendor.packaging.markersr_vendor.packaging.markersetsrcollections.abcrr AbstractSetr KIND_EXTRA KIND_GROUPMARKER_VARIABLE_FOR_KINDvaluesr1r __annotations__compilejoinrr ValueErrorrr,r5)variabler6s0@rrGs# :3'21   #+C*I*I*K4*Khik*K40** SXX.557 886A -Z" 3,i4sC