q"h+ FSSKrSSKJr SSKJrJrJrJrJrJ r J r J r J r J r SSKJr SSKJr SSKJrJrJr SSKJr SS KJr SS KJr \(aSS KJr SS KJr \\\4r\\\\ 4r!O\r!\ "S 5r"\ "S5r#S\\ \#4S\ S\"S\ \"\#44Sjr$"SS\!5r%g)N) lru_cache) TYPE_CHECKINGDictIterableIteratorMappingOptionalSequenceTupleTypeVarUnion)AbstractProvider)InstallRequirement) Candidate Constraint Requirement)REQUIRES_PYTHON_IDENTIFIER)Factory)ExplicitRequirement) Preference)RequirementInformationDVmapping identifierdefaultreturnc`X;aX$URS5up4nU(a X0;aX$U$)aUGet item from a package name lookup mapping with a resolver identifier. This extra logic is needed when the target mapping is keyed by package name, which cannot be directly looked up with an identifier (which may contain requested extras). Additional logic is added to also look up a value by "cleaning up" the extras from the identifier. [) partition)rrrname open_bracket_s ^/var/www/html/env/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/provider.py_get_with_identifierr&:s>"" '005D} Nc \rSrSrSrS\S\\\4S\ S\S\\\ 4SS 4 S jr S \ \ \4S\4S jrS \\S\\\4S\\\\4S\\\S4S\SS\\4 SjrS\S\\\4S\\\\4S\\\S4S\SSS4 SjrS\S\\\\ 4S\\\\4S\\4Sjr\\"S S9S\ S\S\ 4Sj55rS\S\\ 4SjrSrg ) PipProviderSaPip's provider implementation for resolvelib. :params constraints: A mapping of constraints specified by the user. Keys are canonicalized project names. :params ignore_dependencies: Whether the user specified ``--no-deps``. :params upgrade_strategy: The user-specified upgrade strategy. :params user_requested: A set of canonicalized package names that the user supplied for pip to install/upgrade. factory constraintsignore_dependenciesupgrade_strategyuser_requestedrNc@XlX lX0lX@lXPlgN)_factory _constraints_ignore_dependencies_upgrade_strategy_user_requested)selfr+r,r-r.r/s r%__init__PipProvider.__init__^s! '$7!!1-r'requirement_or_candidatecUR$r1)r")r7r:s r%identifyPipProvider.identifyls',,,r' identifiers resolutions candidates informationPreferenceInformationbacktrack_causescT[5nUH\nURURR5 URcM7URURR5 M^ /nUH*n U [ :XaU /s $X;dMUR U 5 M, U(aU$U$)a9Produce a subset of identifiers that should be considered before others. Currently pip narrows the following selection: * Requires-Python, if present is always returned by itself * Backtrack causes are considered next because they can be identified in linear time here, whereas because get_preference() is called for each identifier, it would be quadratic to check for them there. Further, the current backtrack causes likely need to be resolved before other requirements as a resolution can't be found while there is a conflict. )setadd requirementr"parentrappend) r7r>r?r@rArCbacktrack_identifiersinfocurrent_backtrack_causesrs r%narrow_requirement_selection(PipProvider.narrow_requirement_selectionos&!$$D ! % %d&6&6&;&; <{{&%))$++*:*:;% $& %J77"|#2(// ;& $+ +r'rrc[[XA55 SnU(dSnSnO[SXA56up[ U 5nSU5V V s/sH%n U Hn U R U R 4PM M' n n n [ SU 55n [ SU 55n[U 5nURRU[R5nU(+U (+U(+UU(+U4$![a SnNf=fs sn n f)aProduce a sort key for given requirement based on preference. The lower the return value is, the more preferred this group of arguments is. Currently pip considers the following in order: * Any requirement that is "direct", e.g., points to an explicit URL. * Any requirement that is "pinned", i.e., contains the operator ``===`` or ``==`` without a wildcard. * Any requirement that imposes an upper version limit, i.e., contains the operator ``<``, ``<=``, ``~=``, or ``==`` with a wildcard. Because pip prioritizes the latest version, preferring explicit upper bounds can rule out infeasible candidates sooner. This does not imply that upper bounds are good practice; they can make dependency management and resolution harder. * Order user-specified requirements as they are specified, placing other requirements afterward. * Any "non-free" requirement, i.e., one that contains at least one operator, such as ``>=`` or ``!=``. * Alphabetical order for consistency (aids debuggability). TFc3l# UH*up[U[5UR5S4v M, g7f)rN) isinstancerget_candidate_lookup).0rr$s r% -PipProvider.get_preference..s5 7 #679O9O9QRS9TU 7s24c3J# UHo(dM URv M g7fr1) specifier)rTireqs r%rVrWs!KUTd.$..Us ##c3N# UHupUSSS:H=(a SU;v M g7f)N==*rPrTopvers r%rVrWs(VIr"1v~;CsN;Is#%c3`# UH$upUS;=(d US:H=(a SU;v M& g7f))@E ! + 7NG \F"LU!K, !K *   !2!2 3* 4!K , VIVV $  i..22:txxHJJ  J    I $$O $,, sC4,D4 DD requirementsincompatibilitiesc ^S[S[4U4Sjjn[TRU[R "5S9nTR RUUUU"U5(+UTRS9$)Nrrcz>TRS:XagTRS:Xa[TRUSS9nUSL$g)aAre upgrades allowed for this project? This checks the upgrade strategy, and whether the project was one that the user specified in the command line, in order to decide whether we should upgrade if there's a newer version available. (Note that we don't need access to the `--upgrade` flag, because an upgrade strategy of "to-satisfy-only" means that `--upgrade` was not specified). eagerTzonly-if-neededNrF)r5r&r6)r user_orderr7s r%_eligible_for_upgrade7PipProvider.find_matches.._eligible_for_upgradesN%%0''+;;1((  "--r'r)rr{ constraintprefers_installedr|is_satisfied_by) strrkr&r3remptyr2find_candidatesr)r7rr{r|rrs` r% find_matchesPipProvider.find_matchessx  c d ,*    $$& }},,!%!#8#DD/ 00 -  r')maxsizerG candidatec$URU5$r1)r)rGrs r%rPipProvider.is_satisfied_bys**955r'cTUR(+nSURU55$)Nc3.# UH ocMUv M g7fr1rP)rTrUs r%rV/PipProvider.get_dependencies..sWEaEs )r4iter_dependencies)r7r with_requiress r%get_dependenciesPipProvider.get_dependenciess& 555 W966}EWWr')r3r2r4r5r6)__name__ __module__ __qualname____firstlineno____doc__rrrrrkintr8r rrr<rrrr rMryr staticmethodrrr__static_attributes__rPr'r%r)r)Ss . .#z/* ." .  . S#X .  .-{I7M1N-SV-)c])S)^,)C)!445 ) S(+B"CCD ) ##:; ) #)VK K S)^,K C)!445 K S(+B"CCD K ##:; K  K Z( ( c8K#889( #3(;#;< ( )  ( Tt6[6Y6466X)X8MXr'r))&rm functoolsrtypingrrrrrr r r r r pip._vendor.resolvelib.providersrpip._internal.req.req_installrbaserrrr@rr+rr{rr pip._vendor.resolvelib.resolversrrBr _ProviderBaserrr&r)rPr'r%rs    ><442-;G2; 3IJ$[)S%@AM$M* CL CL S!V_ 1a4[ 2FX-FXr'