+ 2jHzRt^RIHt^RIt^RIHt^RIHt^RIH t H t H t ^RI H t Ht^RIHt]'d^RIHtHt^R IHt^R IHt^R IHtR .t^tR t!RR ]4tRR+RR+/RRlltRRlt RRlt!RRlt"RRlt#RRlt$RRlt%RR lt&R!R"lt'R#R$lt(R%R&lt)R,R'R(llt*R)R*lt+R#)-a-Per-name marker disjointness validation for the PEP 751 emitter. PEP 751 forbids two ``[[packages]]`` entries with the same name from firing under one install context. This module owns the validator that decides, for every same-name pair, whether their markers can hold together under the declared install-context universe (declared environments, with conflict-forbidden co-selections excluded). The universe is not expressible as a single PEP 508 marker string, so the check runs through the marker algebra. For each same-name pair and each declared environment the validator restricts both markers to the environment, then walks the conflict-respecting selections of the membership names the pair references: each conflict set contributes at most one active member, names in no conflict set are free, and undeclared names stay absent. The pair collides when both residuals still fire together under some selection. Only the referenced names enter the walk, so the cost tracks the pair's own markers rather than the ``powerset(extras) x powerset(groups)`` grid. ) annotationsN) defaultdict) TYPE_CHECKING) KIND_EXTRA KIND_GROUPMARKER_VARIABLE_FOR_KIND)IntractableMarkerSet MarkerSet)canonicalize_name)MappingSequence)Set)Marker)PackageDisjointnessErroric]tRt^4tRtRtR#)raTwo same-name ``[[packages]]`` entries can fire under one context. PEP 751 forbids ambiguous installer matches. When more than one same-name entry has a marker that holds for the same install context, the consumer cannot pick deterministically. The validator surfaces the colliding name and the witness environment. When the reported collision reduces to a concrete point it also reports the active extras and groups and the colliding versions; when that collision is an over-approximated ``contains`` region the algebra cannot pin to a point, it reports only the name and environment. Either way the producer can change the resolution or declare a conflict. N)__name__ __module__ __qualname____firstlineno____doc____static_attributes__rl/home/user/billing-ledger-validation/.venv/lib/python3.14/site-packages/nab_python/_lockfile/disjointness.pyrr4s rexclusive_groupsdeclared_groupsc4V^8dQhRRRRRRRRRR R R R R /#) packagesSequence[Package] environmentsMapping[str, Mapping[str, str]]extras Sequence[str]groupsr&Sequence[AbstractSet[tuple[str, str]]]rreturnNoner)formats"r __annotate__r*DsYHHH2H  H  H = H<H Hrc &V'gR#\\4pVF.pV\VP4,P V4K0 VP 4Uu.uFp\ V4^8gKVNK p pV 'gR#\V4p \V4p \W#4p V FpVUu.uFp\VP4NK p pV Uu.uFqP4NK pp\P!\\ V44^4F`wppVV,VV,,p\!VW4p\#V V,V V,VV 4pVfKKVwppp\%WVVVV4Kb K R#uupiuupiuupi)aConfirm same-name ``[[packages]]`` entries are pairwise disjoint. For every same-name pair the validator asks the marker algebra whether the two markers can hold together within the declared install-context universe. The universe is the declared environments on the environment axes, with the extras and dependency-group axes restricted so that no conflict set has two active members (``exclusive_groups``) and no name outside the declared ``extras`` / ``groups`` is ever selected. A pair collides when, in some declared environment, both markers still fire under a conflict-respecting selection of the membership names they reference. The empty-environments path skips validation: a producer that does not declare a universe cannot specify what "all envs" means and the validator would over-report when entries have ``marker is None``. Every resolve declares one environment per target, so that path is reached only by a caller that builds a :class:`~nab_python.lockfile.LockInput` with no targets of its own. ``exclusive_groups`` declares mutually-exclusive selections from ``[tool.nab].conflicts``: each entry is a set of ``(kind, name)`` members (``kind`` is ``"extra"`` or ``"group"``) of which at most one may be active. Their co-selection points are removed from the universe, so a same-name pair that can fire together only at a forbidden co-selection is not counted as a collision. A collision outside every pruned point still raises, hinting at the ``conflicts`` key when extras or groups drive the colliding markers. ``declared_groups`` carries every conflict set regardless of policy so the hint can distinguish an undeclared collision (suggest adding a declaration) from one already declared under ``at-least-one`` (suggest tightening to ``at-most-one`` or ``exactly-one``). N)rliststrnameappendvalueslen_distinct_environments_canonical_exclusion_sets_declared_membership_literals _marker_setmarkermembership_literals itertools combinationsrange_conflict_respecting_selections_pair_collision_raise_collision)rr!r#r%rrby_namepkgentriessame_name_entriesdistinct_environmentsexclusion_setsdeclared_members marker_setsmsliteralsijnames selections collisionlabelenv witness_envs&$$$$$ rvalidate_marker_disjointnessrPDsiV /:4/@GCHH %%c*070@U0@WCLSTDT0@U 2<@./?@N4VD$:AB'3{3::.' B7BC{**,{C**5W+>BDAqQK(1+-E8~J(A A ,_canonical_exclusion_sets..s) % &d +->t-D E%s')) frozenset)rmemberss& rr3r3s?(   (G  %  (   s#c$V^8dQhRRRRRR/#)rr#r$r%r'frozenset[tuple[str, str]]r)r)s"rr*r*s$ #0rc \\,p\\,p\VUu0uFqB\ V43kK upVUu0uFqC\ V43kK up,4#uupiuupi)zReturn every ``(variable, canonical name)`` the universe may select. A membership literal outside this set names an extra or group the producer never declared, so no install context selects it; the universe pins it absent. )rrrrhr )r#r% extras_var groups_varr.s&& rr4r4sg**5J)*5J ;AB64'- .6B=C DVT)$/ 0V D E B Ds A)A. c(V^8dQhRRRRRRRR/#)rrJrkrCr&rDr'zlist[dict[str, frozenset[str]]]r)r)s"rr*r*s0,, %,:,1,% ,rc "\RV44pW,pVUu.uF$qUV,'gK\WT,4NK& ppVUUu0uF qwFqkK K p pp\WI, 4p VUu.uFp\V4^,NK up^.\V 4,,p ^p V F*p W,p V \8gKR\ 2p\ V4h VUUu.uF/p\4.VUu.uFp\V04NK up,NK1 ppp.p\ P !V!Fp\4P!V!p\VV4'gK/\^\V 4,4FhpT\\V 44Uu0uF$pV^V,,'gKV V,kK& up,pVP\VV44Kj K V#uupiuuppiuupiuupiuuppiuupi)aUEnumerate the membership selections the pair's markers can see. A selection binds every membership variable the pair references to a concrete set of active names. Only declared names can be active, so an undeclared reference stays absent in every selection. Each conflict set that touches the referenced names contributes at most one active member; names in no conflict set are free and appear in both states. The count is the product of the per-conflict-set choices and the free powerset, guarded by :data:`_MAX_SELECTIONS` so a pathological input fails loud rather than iterating unbounded. c3*"TF wrVxK R#5ircr)rdvariable_s& rrf2_conflict_respecting_selections..sBE[XEsz&conflict-respecting selections exceed ) rhrVr1_MAX_SELECTIONSrr8productunion_conflict_respectingr:r/_selection_env)rJrCrDreferenced_varsdeclaredriconflict_choiceschoicemember constrainedfreecountssizecountmsg group_optionsrKcombobasemaskkactives&&& rr;r;s  BEBBO'H2@2@whDVDV"w!".)9N(8fvV6v6(8KN (( )D,< =,<&c&kAoo,< =c$i OF D  / !:?:KLC&s+ + '&F  6B6F8,6BBB&35J""M2{  %(#D.99 !s4y.)DeCI.>R.>$!q&//WT!WW.>RRF   n_fE F* 3 5O>CSs:G1G1G6:G<'H:H HH 6 H Hc$V^8dQhRRRRRR/#)rrrkrCr&r'boolr)r)s"rr*r*s& &: rcxa\;QJdV3RlV4F 'dK R# R#!V3RlV44#)z=Whether no conflict set has two active members in ``active``.c3V<"TFp\VS,4\8xK R#5irc)r1_MUTUALLY_EXCLUSIVE_LIMIT)rdrirs& rrf'_conflict_respecting..s$IWgGf  99s&)FT)all)rrCsf&rrxrxs@ 3IW3333IW rc$V^8dQhRRRRRR/#)rrzfrozenset[str]rrkr'zdict[str, frozenset[str]]r)r)s"rr*r* s) O O# O-G O OrcVUu/uF q"\4bK ppVFwr$W2,PV4K VP4UUu/uFwr%V\V4bK upp#uupiuuppi)aGroup an active selection into a per-variable ``restrict`` mapping. Every referenced membership variable is bound, even to the empty set, so a marker's membership atoms all fold to constants under the resulting restriction rather than leaving a residual axis. )rSrWrTrh)rzrrrgroupedr.rJs&& rryry snET#TOceOOG#T d#!>Emmo No?8Hi& &o NN$U Os A*A/c ,V^8dQhRRRRRRRRRR /#) rleftr rightrKz#Sequence[dict[str, frozenset[str]]]rBz'Sequence[tuple[str, Mapping[str, str]]]r'zLtuple[str, Mapping[str, str], dict[str, str | frozenset[str]] | None] | Noner)r)s"rr*r*s<  4C  R rc<VFwrEVPV4pVPV4pVFhpVPV4VPV4,p V P4'dKBV P4p V f WER3uu#WE/V CVC3uu# K R#)aReturn a declared env where both markers can fire together, or None. Each marker is restricted to the environment (its environment atoms fold to constants, leaving the membership residual). Each conflict-respecting selection binds the membership variables, so the pair collides in that environment when both bound residuals stay non-empty together. On a collision the label, the environment, and a concrete satisfying assignment (the selection merged with :meth:`MarkerSet.witness`) are returned; the witness is ``None`` when the first colliding selection is an opaque-``contains`` over-approximation the algebra cannot reduce to a point. N)restrictis_emptywitness) rrrKrBrMrN left_here right_here selectionrLrs &&&& rr<r<s$, MM#& ^^C( #I!**95 8K8KI8VVI!!##'')G4''7'7Y77 7$, rc$V^8dQhRRRRRR/#)rrOz"Mapping[str, str | frozenset[str]]rrr-r'rr)r)s"rr*r*8s$3?BrchVPV4p\V\4'dV#\4#)z>Return the set the witness selected for a membership variable.)get isinstancerh)rOrrvalues&& r_membership_selectionr8s, OOH %E%## ;rc4V^8dQhRRRRRRRRR R R R R R/#)rr@r rESequence[MarkerSet]rMr-rNzMapping[str, str]rOz&dict[str, str | frozenset[str]] | Nonerr&r'r(r)r)s"rr*r*BsN6!6! 6!$6! 6!  6! 8 6! < 6! 6!rc \V^,P4pVfV RV: 2p\V4h\\,p\\ ,p \ WH4p \ WI4p /VCVCWW/Cp \WRR7U Uu.uF/wrVPV 4P4'dK,W3NK1 pp p\V 4p\V 4p\RV44p\VUUu.uFwpqNK uppVVV4pV R\V4 RV: RV: RV: R V V 2 p\V4huupp iuuppi) aRaise :class:`DisjointnessError` with a concrete witness context. The witness names one install context where the pair holds together, so the message reports the environment, the active ``(extras, groups)`` selection, the entries that fire there, and their versions. When the reported collision has no pinned point (an opaque-``contains`` over-approximation), the pair is still reported as non-disjoint, without a point. z/: same-name entries are not disjoint under env=T)strictc3x"TF0wrVP'd\VP4MRxK2 R#5i)N)versionr-)rdprss& rrf#_raise_collision..ns'Ohda c!))nr9hs8:z: z entries fire under env=z extras=z groups=z : versions=) r-r.rrrrrziprrrV_conflict_hintr1)r@rErMrNrOrr.rrmrnextra_selectiongroup_selectionpointr?rFmatching extra_subset group_subsetversionsrshints&&&&&& rr=r=Bsj" wqz DEeYO$$)*5J)*5J+KDO+KDO 0 0 0  0E7==GC{{5!**,  =  /*L/*LOhOOH !"2"L, D &3x=/"y 0 <"+hZ &  C  % #s)D44D40 D: c ,V^8dQhRRRRRRRRRR /#) rrErrr$rrr&r'r-r)r)s"rr*r*{s:..$.. .< .  .rca\V\\,V4p\V\\,V4pV'g V'gR#VUu0uFp\\ V43kK upVUu0uFp\\ V43kK up,o\ ;QJdV3RlV4F 'gK RM RM!V3RlV44pV'dR#R#uupiuupi)aReturn a one-line hint about declaring a conflict, when relevant. Relevant means a membership variable actually drives the witness point: a referenced extra or dependency group is active in the colliding context, so declaring the pair mutually exclusive in ``[tool.nab].conflicts`` could prune that point. A purely environment-driven collision (no membership variable referenced, or the witness selects none of the referenced ones) gets no hint because a conflict declaration would not help. When ``declared_groups`` already covers the active members, the hint instead suggests tightening the policy: an ``at-least-one`` declaration permits co-selection, so the validator still raises and the user has to switch to an exclusive policy to prune the point. rc3T<"TFp\V3RlV44^8xK R#5i)c3@<"TFwrW3S9gK^xK R#5i)Nr)rdrer.rs& rrf+_conflict_hint...s C*$TLF,BAAs  N)sum)rdr{rs& rrf!_conflict_hint..s('H C CCqH's%(TFz. These members are declared in [tool.nab].conflicts under a policy that permits co-selection; switch to at-most-one or exactly-one to prune the colliding contextzx. If these are intentionally mutually exclusive, declare them in [tool.nab].conflicts so the colliding context is pruned)_membership_drives_pointrrrr any) rErrr extras_driven groups_drivennalready_declaredrs &&&& @rrr{s*--j9<M--j9<M ]:F G,Qz,Q/0, G4@K4@q&q)*LKFs'sss' :  CHKs C0C c(V^8dQhRRRRRRRR/#) rrErrrr-subsetr$r'rr)r)s"rr*r*s,66$6036=J6 6rcFaVUUUu0uF&pVP4FwrEWA8XgK VkK K( ppppV'gR#VUu0uFp\V4kK upo\;QJdV3RlV4F 'gK R# R#!V3RlV44#uupppiuupi)a>Return True when a referenced ``variable`` literal is active here. A membership variable drives the witness only when the witness ``subset`` is non-empty and intersects the literals the colliding markers test for membership in ``variable`` (compared under canonicalisation, matching the universe's axis restriction). Fc3,<"TF qS9xK R#5ircr)rdr.rs& rrf+_membership_drives_point..s5*$v~*sT)r7r r)rErrr marker_setvarr. referencedrs&&& @rrrs&%J#779IC ? 9 % 28 9&$%& 9F 35*53353535*5 55:sB BBr)r),r __future__rr8 collectionsrtypingr_conflict_kindrrr_vendor.packaging.markersetsrr _vendor.packaging.utilsr collections.abcr r r AbstractSet_vendor.packaging.markersr_vendor.packaging.pylockr__all__rru ValueErrorrrPr2r5r3r4r;rxryr<rr=rrrrrrs(## MMJ71222     H @B H?AHV,)&",^ O@6!r.b6r