a e0h@sddlmZddlmZddlmZerlddlmZmZm Z m Z m Z m Z m Z mZddlmZmZddlmZGdd d eZd S) )AbstractProvider)MYPY_CHECK_RUNNING) Constraint)AnyDictIterableOptionalSequenceSetTupleUnion) Candidate Requirement)Factoryc@s@eZdZdZddZddZddZdd Zd d Zd d Z dS) PipProvideraPip'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. cCs"||_||_||_||_||_dSN)_factory _constraints_ignore_dependencies_upgrade_strategy_user_requested)selffactory constraintsignore_dependenciesupgrade_strategyuser_requestedrZ/var/www/auris/lib/python3.9/site-packages/pip/_internal/resolution/resolvelib/provider.py__init__+s zPipProvider.__init__cCs|jSrname)r dependencyrrridentify:szPipProvider.identifyc CsVdd}|dd|D}tdd|D}|r>tt|jnd}|dk}||||fS)azProduce 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 followings in order: * Prefer if any of the known requirements points to an explicit URL. * If equal, prefer if any requirements contain ``===`` and ``==``. * If equal, prefer if requirements include version constraints, e.g. ``>=`` and ``<``. * If equal, prefer user-specified (non-transitive) requirements. * If equal, order alphabetically for consistency (helps debuggability). cSsndd|D}t|\}}tdd|Dr0dSdd|D}dd|D}tdd|Drbd S|rjd Sd S) aRate how restrictive a set of requirements are. ``Requirement.get_candidate_lookup()`` returns a 2-tuple for lookup. The first element is ``Optional[Candidate]`` and the second ``Optional[InstallRequirement]``. * If the requirement is an explicit one, the explicitly-required candidate is returned as the first element. * If the requirement is based on a PEP 508 specifier, the backing ``InstallRequirement`` is returned as the second element. We use the first element to check whether there is an explicit requirement, and the second for equality operator. css|]}|VqdSr)get_candidate_lookup.0rrrr dzNPipProvider.get_preference.._get_restrictive_rating..css|]}|duVqdSrr)r'candrrrr)fr*rcss|]}|r|jVqdSr) specifier)r'ireqrrrr)hr*cSsg|]}|D] }|jq qSr)operator)r'spec_setr,rrr iszOPipProvider.get_preference.._get_restrictive_rating..css|]}|dvVqdS))z==z===Nr)r'oprrrr)nr*r)zipany) requirementslookupscandsireqs spec_sets operatorsrrr_get_restrictive_ratingTs z;PipProvider.get_preference.._get_restrictive_ratingcss|]\}}|VqdSrr)r'req_rrrr)ur*z-PipProvider.get_preference..css|]\}}|duVqdSrr)r'r>parentrrrr)vr* setuptools)allnextiterr") r resolution candidates informationr< restrictive transitivekey delay_thisrrrget_preference>s ! zPipProvider.get_preferencecsD|sgS|dj}fdd}jj|j|t|| dS)Nrcs&jdkrdSjdkr"|jvSdS)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-neededF)rrr!rrr_eligible_for_upgrades   z7PipProvider.find_matches.._eligible_for_upgrade) constraintprefers_installed) project_namerfind_candidatesrgetrempty)rr6r"rOrrNr find_matchess  zPipProvider.find_matchescCs ||Sr)is_satisfied_by)r requirement candidaterrrrWszPipProvider.is_satisfied_bycCs|j }dd||DS)NcSsg|]}|dur|qSrrr&rrrr0sz0PipProvider.get_dependencies..)riter_dependencies)rrY with_requiresrrrget_dependenciesszPipProvider.get_dependenciesN) __name__ __module__ __qualname____doc__r r$rLrVrWr\rrrrr s GrN) pip._vendor.resolvelib.providersrpip._internal.utils.typingrbasertypingrrrr r r r r rrrrrrrrrs   (