a 0f^@sdZddlZddlZddlmZddlmZddlmZm Z m Z m Z m Z m Z ddlmZddlmZddlmZdd lmZmZmZmZmZmZmZdd lmZdd lmZdd l m!Z!dd l"m#Z#ddl$m%Z%ddl&m'Z'm(Z(ddl)m*Z*ddl+m,Z,m-Z-ddl.m/Z/ddl0m1Z1ddl2m3Z3ddl4m5Z5ddl6m7Z7ddl8m9Z9e:e;Zdee e?e?e?fe@ddddZAGddde,ZBdS)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) DefaultDictIterableListOptionalSetTuple) specifiers) Requirement) WheelCache)BestVersionAlreadyInstalledDistributionNotFound HashError HashErrorsInstallationErrorNoneMetadataErrorUnsupportedPythonVersion) PackageFinder)BaseDistribution)Link)Wheel)RequirementPreparer)InstallRequirementcheck_invalid_constraint_type)RequirementSet) BaseResolverInstallRequirementProvider)compatibility_tags) get_supported)direct_url_from_link) indent_log)normalize_version_info)check_requires_pythonF)dist version_infoignore_requires_pythonreturnc Cszt|j}Wn2ty@}zt|t|WYd}~n d}~00zt||d}Wn8tjy}ztd|j |WYd}~dSd}~00|rdSd t t|}|rt d|j ||dSt d|j d|d|dS) a Check whether the given Python version is compatible with a distribution's "Requires-Python" value. :param version_info: A 3-tuple of ints representing the Python major-minor-micro version to check. :param ignore_requires_python: Whether to ignore the "Requires-Python" value if the given Python version isn't compatible. :raises UnsupportedPythonVersion: When the given Python version isn't compatible. N)r%z-Package %r has an invalid Requires-Python: %s.zBIgnoring failed Requires-Python check for package %r: %s not in %rzPackage z requires a different Python: z not in )strrequires_pythonFileNotFoundErrorrr#r InvalidSpecifierloggerwarningraw_namejoinmapdebugr)r$r%r&r*e is_compatibleexcversionr7a/var/www/ai-form-bot/venv/lib/python3.9/site-packages/pip/_internal/resolution/legacy/resolver.py_check_dist_requires_python7s@$  r9cs2eZdZdZhdZd"eeeee e e e e e e ee e dfdd fdd Zeee edd d Zd#eeee eee e eeeefd d d Zee dddZeddddZeee dddZeeedddZeddddZeedddZeeeedddZeeedd d!ZZS)$ResolverzResolves which packages need to be installed/uninstalled to perform the requested operation without breaking the requirements of any package. >to-satisfy-onlyeageronly-if-neededN.) preparerfinder wheel_cachemake_install_req use_user_siteignore_dependenciesignore_installedr&force_reinstallupgrade_strategypy_version_infor'c st| |jvsJ| dur0tjdd} nt| } | |_||_||_||_ | |_ | |_ ||_ ||_ ||_||_||_tt|_dS)N)super__init___allowed_strategiessysr%r"_py_version_infor>r?r@rFrErCrDr&rB_make_install_reqrlist_discovered_dependencies) selfr>r?r@rArBrCrDr&rErFrG __class__r7r8rJts" zResolver.__init__) root_reqscheck_supported_wheelsr'c Cst|d}|D]}|jr t||||qg}t}t|j|D]P}z||||WqDt y}z||_ | |WYd}~qDd}~00qD|r||S)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. )rUN) r constraintr_add_requirement_to_setrrall_requirementsextend _resolve_onerreqappend)rQrTrUrequirement_setr[Zdiscovered_reqsZ hash_errorsr5r7r7r8resolves "zResolver.resolve)r] install_reqparent_req_nameextras_requestedr'c Cs||s$td|j|jgdfS|jrf|jjrft|jj}t }|j rf| |sft |jd|jr||dus|Jd|js|||gdfSz||j}Wntyd}Yn0|duo|o|j o|j|jko|jo|jo|jj|jjk}|rt d|d|d|jd|s8|||g|fS|jsH|jsPg|fS|jop|jon|jj|jjk } | rt d |jd d |_|jrd |_ttt|jt|jB|_td ||j|g|fS)a&Add install_req as a requirement to install. :param parent_req_name: The name of the requirement that needed this added. The name is used because when multiple unnamed requirements resolve to the same name, we could otherwise end up with dependency links that point outside the Requirements set. parent_req must already be added. Note that None implies that this is a user supplied requirement, vs an inferred one. :param extras_requested: an iterable of extras used to evaluate the environment markers. :return: Additional requirements to scan. That is either [] if the requirement is not applicable, or [install_req] if the requirement is applicable and has just been added. z6Ignoring %s: markers '%s' don't match your environmentNz+ is not a supported wheel on this platform.z+a user supplied req shouldn't have a parentzDouble requirement given: z (already in z, name=)z#Could not satisfy constraints for 'zC': installation from path or url cannot be constrained to a versionFTzSetting %s extras to: %s) match_markersr-infonamemarkerslinkis_wheelrfilenamerrrU supportedr user_suppliedadd_unnamed_requirementget_requirementKeyErrorrVextrasr[ specifieradd_named_requirementpathtuplesortedsetr2) rQr]r_r`rawheeltagsZ existing_reqZhas_conflicting_requirementZdoes_not_satisfy_constraintr7r7r8rWs             z Resolver._add_requirement_to_setr[r'cCs:|jdkrdS|jdkrdS|jdks*J|jp4|jSdS)Nr;Fr<Tr=)rFrkrVrQr[r7r7r8_is_upgrade_allowed2s   zResolver._is_upgrade_allowedcCs,|jdusJ|jr|jjr"d|_d|_dS)z4 Set a requirement to be installed. NT) satisfied_byrB in_usersiteshould_reinstallryr7r7r8_set_req_to_reinstall;szResolver._set_req_to_reinstall)req_to_installr'cCs|jr dS||j|js dS|jr4||dS||sP|jdkrLdSdS|jsz|j j |ddWn$t y~YdSt yYn0||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. Nr=z#already satisfied, skipping upgradezalready satisfiedT)upgradezalready up-to-date) rDcheck_if_existsrBr{rEr~rzrFrgr?find_requirementr r)rQrr7r7r8_check_skip_installedFs*       zResolver._check_skip_installedcCsT||}|j||}|s dS|j}|jrP|jp4d}d|d|}t||S)Nz zDThe candidate selected for download or install is a yanked version: z Reason for being yanked: )rzr?rrg is_yanked yanked_reasonr-r.)rQr[rbest_candidatergreasonmsgr7r7r8_find_requirement_link|s   zResolver._find_requirement_linkcCs|jdur|||_|jdus(|jjr,dS|jdus>Jd|jj|j|jtd}|durt d|j|j|j ur|j r|j|_ |j dur|j |_nt|j|j d|_|j|_dS)afEnsure that if a link can be found for this, that it is found. Note that req.link may still be None - if the requirement is already installed and not needed to be upgraded based on the return value of _is_upgrade_allowed(). If preparer.require_hashes is True, don't use the wheel cache, because cached wheels, always built locally, have different hashes than the files downloaded from the index server and thus throw false hash mismatches. Furthermore, cached wheels at present have undeterministic contents due to file modification times. Nz1_find_requirement_link unexpectedly returned None)rg package_namesupported_tagszUsing cached wheel link: %s)link_is_in_wheel_cache)rgrr@r>require_hashesget_cache_entryrerr-r2 original_link persistentZcached_wheel_source_linkorigin download_infor )rQr[ cache_entryr7r7r8_populate_links(    zResolver._populate_linkcCs|jr|j|S|jdus J||}|jr>|j||S|||j|}|jsf| |j |jr|j dkp|j p|jp|j jdk}|r||n td||S)zzTakes a InstallRequirement and returns a single AbstractDist representing a prepared variant of the same. Nr;filezprepare_editable_requirementr{rprepare_installed_requirementrprepare_linked_requirementrDrrBrFrErgschemer~r-rd)rQr[ skip_reasonr$Z should_modifyr7r7r8 _get_dist_fors2        zResolver._get_dist_for)r]rr'c sHjs jrgSd_}t|jjdgtttddfdd }t j duslJ j sj sJj ddjs$jrtdd jttjt|}|D]}td |j|j|qtt|tj@}||D]}|||d qWdn1s:0YS) zxPrepare a single requirements file. :return: A list of additional InstallRequirements to also install. T)r%r&N)subreqrar'csRt|}j}j|||d\}}|rD|rDj|||dS)N)r`ra)rNr)rerWrPr\rY)rraZsub_install_reqr`Z to_scan_againZ add_to_parentZ more_reqsrr]rQr7r8add_reqs z&Resolver._resolve_one..add_req)r`z!Installing extra requirements: %r,z%%s %s does not provide the extra '%s')ra)rVpreparedrr9rMr&r rr)r!rehas_requirementrkrWrCror-r2r0rtruiter_provided_extrasr.r/r6iter_dependencies) rQr]rr$rZmissing_requestedmissingZavailable_requestedrr7rr8rZsP      0zResolver._resolve_one)req_setr'cs@gttddfdd |jD] }|q.S)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. NrxcsN|js|vrdS|jrdS|j|jD] }|q2|dS)N)r{rVaddrPrer\)r[deporderZ ordered_reqsschedulerQr7r8rIs  z1Resolver.get_installation_order..schedule)rur requirementsvalues)rQrr_r7rr8get_installation_order:s   zResolver.get_installation_order)N)NN) __name__ __module__ __qualname____doc__rKrrrr rboolr)r intrJrrrr^rrWrzr~rrrrrrrZr __classcell__r7r7rRr8r:msX' )  s   6'0 Tr:)F)CrloggingrL collectionsr itertoolsrtypingrrrrrr Zpip._vendor.packagingr "pip._vendor.packaging.requirementsr pip._internal.cacher pip._internal.exceptionsr rrrrrr"pip._internal.index.package_finderrpip._internal.metadatarpip._internal.models.linkrpip._internal.models.wheelr pip._internal.operations.preparerZpip._internal.req.req_installrrZpip._internal.req.req_setrpip._internal.resolution.baserrZpip._internal.utilsr&pip._internal.utils.compatibility_tagsr&pip._internal.utils.direct_url_helpersr pip._internal.utils.loggingr!pip._internal.utils.miscr"pip._internal.utils.packagingr# getLoggerrr-r)ZDiscoveredDependenciesrrr9r:r7r7r7r8sB       $               6