OwlCyberSecurity - MANAGER
Edit File: resolver.cpython-310.pyc
o ƚReH � @ s� d Z ddlZddlZddlmZ ddlmZ ddlmZm Z m Z m Z m Z m Z ddlmZ ddlmZ ddlmZ dd lmZmZmZmZmZmZ dd lm Z dd l m Z dd l m Z dd l!m"Z" ddl#m$Z$m%Z% ddl&m'Z' ddl(m)Z)m*Z* ddl+m,Z, ddl-m.Z. ddl/m0Z0m1Z1 ddl/m2Z2 ddl3m4Z4 e�5e6�Z7ee8e e$ f Z9 d de de e:e:e:f de;ddfdd �Z<G d d � d e)�Z=dS ) ay Dependency 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)� DefaultDict�Iterable�List�Optional�Set�Tuple)� specifiers)� Requirement)� WheelCache)�BestVersionAlreadyInstalled�DistributionNotFound� HashError� HashErrors�NoneMetadataError�UnsupportedPythonVersion)� PackageFinder)�BaseDistribution)�Link)�RequirementPreparer)�InstallRequirement� check_invalid_constraint_type)�RequirementSet)� BaseResolver�InstallRequirementProvider)� get_supported)� indent_log)�dist_in_usersite�normalize_version_info)�dist_in_install_path)�check_requires_pythonF�dist� version_info�ignore_requires_python�returnc C s� zt | j�}W n ty } zt| t |���d}~ww zt||d�}W n tjy? } zt�d| j |� W Y d}~dS d}~ww |rDdS d� t t |��}|rYt� d| j ||� dS t d�| j ||���)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 %rz8Package {!r} requires a different Python: {} not in {!r})�str�requires_python�FileNotFoundErrorr r! r �InvalidSpecifier�logger�warning�raw_name�join�map�debugr �format)r" r# r$ r( �e� is_compatible�exc�version� r6 ��/builddir/build/BUILDROOT/alt-python310-pip-21.3.1-3.el8.x86_64/opt/alt/python310/lib/python3.10/site-packages/pip/_internal/resolution/legacy/resolver.py�_check_dist_requires_python7 sD �� �������r8 c s, e Zd ZdZh d�Z d+dededee de de d e d e d e d e d e dee e df ddf� fdd� Zdee de defdd�Zdede fdd�Zdeddfdd�Zd edee fd d �Zdedee fd d �Zdeddfd!d"�Zdedefd#d$�Zd%ed edee fd&d'�Zd(edee fd)d*�Z � Z S ),�Resolverz�Resolves which packages need to be installed/uninstalled to perform the requested operation without breaking the requirements of any package. > �eager�only-if-needed�to-satisfy-onlyN�preparer�finder� wheel_cache�make_install_req� use_user_site�ignore_dependencies�ignore_installedr$ �force_reinstall�upgrade_strategy�py_version_info.r% c s� t � �� | | jv s J �| d u rtjd d� } nt| �} | | _|| _|| _|| _ | | _ | | _ || _ || _ || _|| _|| _tt�| _d S )N� )�super�__init__�_allowed_strategies�sysr# r �_py_version_infor= r> r? rE rD rB rC r$ rA �_make_install_reqr �list�_discovered_dependencies) �selfr= r> r? r@ rA rB rC r$ rD rE rF �� __class__r6 r7 rI u s" zResolver.__init__� root_reqs�check_supported_wheelsc C s� t |d�}|D ]}|jrt|� |�|� qg }t� }t|j|�D ]'}z |�| �||�� W q! t yH } z||_ |� |� W Y d}~q!d}~ww |rM|�|S )a� Resolve 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. )rT N) r � constraintr �add_requirementr r �all_requirements�extend� _resolve_oner �req�append)rP rS rT �requirement_setrZ Zdiscovered_reqsZ hash_errorsr4 r6 r6 r7 �resolve� s$ ��zResolver.resolverZ c C s6 | j dkrdS | j dkrdS | j dksJ �|jp|jS )Nr< Fr: Tr; )rE � user_suppliedrU �rP rZ r6 r6 r7 �_is_upgrade_allowed� s z Resolver._is_upgrade_allowedc C s* | j rt|j�rt|j�rd|_d|_dS )z4 Set a requirement to be installed. TN)rA r � satisfied_byr �should_reinstallr_ r6 r6 r7 �_set_req_to_reinstall� s �� z Resolver._set_req_to_reinstall�req_to_installc C s� | j rdS |�| j� |jsdS | jr| �|� dS | �|�s(| jdkr&dS dS |jsHz | j j |dd� W n t y? Y dS t yG Y nw | �|� dS )a Check 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) rC �check_if_existsrA ra rD rc r` rE �linkr> �find_requirementr r )rP rd r6 r6 r7 �_check_skip_installed� s, � z Resolver._check_skip_installedc C sR | � |�}| j�||�}|sd S |j}|jr'|jpd}dj||d�}t�|� |S )Nz <none given>zqThe candidate selected for download or install is a yanked version: {candidate} Reason for being yanked: {reason})� candidate�reason) r` r> rh rg � is_yanked� yanked_reasonr1 r+ r, )rP rZ re �best_candidaterg rk �msgr6 r6 r7 �_find_requirement_link s � z Resolver._find_requirement_linkc C s� |j du r | �|�|_ | jdu s| jjrdS | jj|j |jt� d�}|dur?t� d|j � |j |j u r9|j r9d|_ |j |_ dS dS )af Ensure 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. N)rg � package_name�supported_tagszUsing cached wheel link: %sT) rg rp r? r= �require_hashes�get_cache_entry�namer r+ r0 � original_link� persistent� original_link_is_in_wheel_cache)rP rZ � cache_entryr6 r6 r7 �_populate_link! s � �zResolver._populate_linkc C s� |j r | j�|�S |jdu sJ �| �|�}|jr | j�||�S | �|� | j�|�}| js3|� | j � |jrV| j dkpF| j pF| jpF|j jdk}|rP| �|� |S t�d|� |S )zzTakes a InstallRequirement and returns a single AbstractDist representing a prepared variant of the same. Nr< �filez<Requirement already satisfied (use --upgrade to upgrade): %s)�editabler= � prepare_editable_requirementra ri � prepare_installed_requirementrz �prepare_linked_requirementrC rf rA rE rD rg �schemerc r+ �info)rP rZ � skip_reasonr" Z should_modifyr6 r6 r7 � _get_dist_for> s4 �� � ��zResolver._get_dist_forr\ c sH �j s�jrg S d�_����}t|�j�jd� g � dtdtt ddf� ���fdd� }t � �j �� �j �sC�j s<J ��j �dd � �js��jrSt�d d ��j�� tt�j�t|�� � �}|D ] }t�d |j|j|� qbtt|�� �t�j�@ �}|�|�D ]}|||d � q�W d � � S W d � � S 1 s�w Y � S )zxPrepare a single requirements file. :return: A list of additional InstallRequirements to also install. T)r# r$ �subreq�extras_requestedr% Nc sP �� t| ���}�j}�j|||d�\}}|r!|r!�j| �|� � �|� d S )N)�parent_req_namer� )rM r' ru rV rO r[ rX )r� r� Zsub_install_reqr� Z to_scan_againZ add_to_parent�Z more_reqsrd r\ rP r6 r7 �add_req� s �z&Resolver._resolve_one.<locals>.add_req)r� z!Installing extra requirements: %r�,z%%s %s does not provide the extra '%s')r� )rU �preparedr� r8 rL r$ r r r' r �has_requirementru r^ rV rB �extrasr+ r0 r. �sorted�set�iter_provided_extrasr, r- r5 �iter_dependencies) rP r\ rd r" r� Zmissing_requested�missingZavailable_requestedr� r6 r� r7 rY l sX �$ ����� �!� �!�!zResolver._resolve_one�req_setc sB g � t � �dtddf� ���fdd� �|j�� D ]}�|� q� S )z�Create 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. rZ r% Nc sN | j s| �v r d S | jrd S ��| � �j| j D ]}�|� q� �| � d S �N)ra rU �addrO ru r[ )rZ �dep��orderZ ordered_reqs�schedulerP r6 r7 r� � s z1Resolver.get_installation_order.<locals>.schedule)r� r � requirements�values)rP r� � install_reqr6 r� r7 �get_installation_order� s z Resolver.get_installation_orderr� ) �__name__� __module__� __qualname__�__doc__rJ r r r r r �boolr' r �intrI r r r r] r` rc ri r rp rz r r� rY r� � __classcell__r6 r6 rQ r7 r9 n st �������� � � � � �&�� �% � �6 .�� �O��r9 )F)>r� �loggingrK � collectionsr � itertoolsr �typingr r r r r r Zpip._vendor.packagingr Z"pip._vendor.packaging.requirementsr �pip._internal.cacher �pip._internal.exceptionsr r r r r r �"pip._internal.index.package_finderr �pip._internal.metadatar �pip._internal.models.linkr � pip._internal.operations.preparer Z pip._internal.req.req_installr r Zpip._internal.req.req_setr � pip._internal.resolution.baser r �&pip._internal.utils.compatibility_tagsr �pip._internal.utils.loggingr �pip._internal.utils.miscr r r � pip._internal.utils.packagingr! � getLoggerr� r+ r' ZDiscoveredDependenciesr� r� r8 r9 r6 r6 r6 r7 �<module> sF �� �� �7