B =)H[s6@sdZddlZddlmZddlmZddlmZmZm Z m Z m Z ddl m Z ddlmZddlmZmZdd lmZeeZGd d d eZdS) ayDependency Resolution The dependency resolution in pip is performed as follows: for top-level requirements: a. only one spec allowed per project, regardless of conflicts or not. otherwise a "double requirement" exception is raised b. they override sub-dependency requirements. for sub-dependencies a. "first found, wins" (where the order is breadth first) N) defaultdict)chain)BestVersionAlreadyInstalledDistributionNotFound HashError HashErrorsUnsupportedPythonVersion)InstallRequirement) indent_log)dist_in_usersite ensure_dir)check_dist_requires_pythoncsbeZdZdZdddhZfddZddZd d Zd d Zd dZ ddZ ddZ ddZ Z S)ResolverzResolves which packages need to be installed/uninstalled to perform the requested operation without breaking the requirements of any package. eagerzonly-if-neededzto-satisfy-onlyc srtt|| |jkst||_||_||_||_d|_ | |_ | |_ | |_ ||_ ||_||_||_tt|_dS)N)superr__init___allowed_strategiesAssertionErrorpreparerfindersession wheel_cacherequire_hashesupgrade_strategyforce_reinstallisolatedignore_dependenciesignore_installedignore_requires_python use_user_siterlist_discovered_dependencies) selfrrrrrrrrrrr) __class__VC:\Users\HIRONO~1\AppData\Local\Temp\pip-install-qz7kpjmn\pip\pip\_internal\resolve.pyr%szResolver.__init__c Cs|jjrt|jj|jt|j}|jp>tdd|D|_|j }|rZt |g}t }x\t||D]N}y||||Wqptk r}z||_||Wdd}~XYqpXqpW|r|dS)aResolve what operations need to be done As a side-effect of this method, the packages (and their dependencies) are downloaded, unpacked and prepared for installation. This preparation is done by ``pip.operations.prepare``. Once PyPI has static dependency metadata available, it would be possible to move the preparation to become a step separated from dependency resolution. css|] }|jVqdS)N)has_hash_options).0reqr$r$r% Vsz#Resolver.resolve..N)rwheel_download_dirr unnamed_requirementsr requirementsvaluesranyrget_formatted_locationsloggerinforrextend _resolve_onerr(append)r"requirement_set root_reqs locationsdiscovered_reqs hash_errorsr(excr$r$r%resolve?s(     zResolver.resolvecCs4|jdkrdS|jdkrdS|jdks*t|jSdS)Nzto-satisfy-onlyFrTzonly-if-needed)rr is_direct)r"r(r$r$r%_is_upgrade_allowedps   zResolver._is_upgrade_allowedcCs"|jrt|jr|j|_d|_dS)z4 Set a requirement to be installed. N)rr satisfied_byconflicts_with)r"r(r$r$r%_set_req_to_reinstallyszResolver._set_req_to_reinstallcCs|jr dS||j|js dS|jr4||dS||sP|jdkrLdSdS|jsy|j j |ddWn&t k r~dSt k rYnX||dS)aCheck if req_to_install should be skipped. This will check if the req is installed, and whether we should upgrade or reinstall it, taking into account all the relevant user options. After calling this req_to_install will only have satisfied_by set to None if the req_to_install is to be upgraded/reinstalled etc. Any other value will be a dist recording the current thing installed that satisfies the requirement. Note that for vcs urls and the like we can't assess skipping in this routine - we simply identify that we need to pull the thing down, then later on it is pulled down and introspected to assess upgrade/ reinstalls etc. :return: A text reason for why it was skipped, or None. Nzonly-if-neededz%not upgraded as not directly requiredzalready satisfiedT)upgradezalready up-to-date) rcheck_if_existsrr>rr@r=rlinkrfind_requirementrr)r"req_to_installr$r$r%_check_skip_installeds*     zResolver._check_skip_installedcCs|jdk std|jr0|j||j|j|jS|jdks>t||}|jr`|j ||j|S| |}|j ||j |j||j}|j s||j|jr|jdkp|jp|j p|jjdk}|r||n td||S)zzTakes a InstallRequirement and returns a single AbstractDist representing a prepared variant of the same. Nz9require_hashes should have been set in Resolver.resolve()zto-satisfy-onlyfilezrFprepare_installed_requirementr=prepare_linked_requirementrrrBrrrCschemer@r0r1)r"r( skip_reasonupgrade_allowed abstract_dist should_modifyr$r$r%_get_abstract_dist_fors6          zResolver._get_abstract_dist_forc s|js jrgSd_j}|j}y t|Wn<tk r}zj rnt |j dnWdd}~XYnXgfdd}t jsd_jddjsRjrt ddjttjt|j}x|D]}t d ||qWtt|jtj@} x || D]} || | d q.add_req)rRz!Installing extra requirements: %r,z"%s does not provide the extra '%s')rS) constraintpreparedreqs_to_cleanupr4rQdistrr rrr0warningargsr has_requirementrVr<rWrextrasdebugjoinsortedsetrequiresrHr>successfully_downloaded) r"r5rErOrberrr]missing_requestedmissingavailable_requestedrXr$)r\rEr5r"r%r3sJ        zResolver._resolve_onecs<gtfddx|jD] }|q(WS)zCreate the installation order. The installation order is topological - requirements are installed before the requiring thing. We break cycles at an arbitrary point, and make no other guarantees. csR|js|krdS|jrdS|xj|jD] }|q4W|dS)N)r>r_addr!rVr4)r(dep)order ordered_reqsscheduler"r$r%ruVs  z1Resolver.get_installation_order..schedule)rjr,r-)r"req_set install_reqr$)rsrtrur"r%get_installation_orderIs   zResolver.get_installation_order)__name__ __module__ __qualname____doc__rrr;r=r@rFrQr3rx __classcell__r$r$)r#r%rs  1  49Xr)r|logging collectionsr itertoolsrpip._internal.exceptionsrrrrrZpip._internal.req.req_installr pip._internal.utils.loggingr pip._internal.utils.miscr r pip._internal.utils.packagingr getLoggerryr0objectrr$r$r$r% s