OwlCyberSecurity - MANAGER
Edit File: legacy_resolve.cpython-38.pyc
U ��.eRC � @ sF d Z ddlZddlZddlmZ ddlmZ ddlmZ ddl m Z m Z m Z m Z mZ ddlmZ ddlmZmZmZmZ dd lmZmZ dd lmZ e�r dd lm Z m Z m Z m Z m Z m!Z! dd l"m#Z# dd l$m%Z% ddl&m'Z' ddl(m)Z) ddl*m+Z+ ddl,m-Z- ddl.m/Z/ e e0e-ge-f Z1e�2e3�Z4ddd�Z5G dd� de6�Z7dS )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)� specifiers)�BestVersionAlreadyInstalled�DistributionNotFound� HashError� HashErrors�UnsupportedPythonVersion)� indent_log)�dist_in_install_path�dist_in_usersite� ensure_dir�normalize_version_info)�check_requires_python�get_requires_python)�MYPY_CHECK_RUNNING)�Callable� DefaultDict�List�Optional�Set�Tuple)� pkg_resources)�AbstractDistribution)� PipSession)� PackageFinder)�RequirementPreparer)�InstallRequirement)�RequirementSetFc C s� t | �}zt||d�}W n: tjk rR } zt�d| j|� W Y �dS d}~X Y nX |r\dS d�tt |��}|r�t� d| j||� dS t d� | j||���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. )� version_infoz-Package %r has an invalid Requires-Python: %sN�.zBIgnoring failed Requires-Python check for package %r: %s not in %rz8Package {!r} requires a different Python: {} not in {!r}) r r r ZInvalidSpecifier�logger�warningZ project_name�join�map�str�debugr �format)�distr �ignore_requires_pythonZrequires_pythonZ is_compatible�exc�version� r, �@/usr/lib/python3.8/site-packages/pip/_internal/legacy_resolve.py�_check_dist_requires_python> s> � � � ��r. c sd e Zd ZdZdddhZd� fdd� Zdd � Zd d � Zd d � Zdd� Z dd� Z dd� Z dd� 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-onlyNc s� t t| ��� | | jks t�| d kr4tjd d� } nt| �} | | _|| _ || _ || _ d | _ | | _ | | _|| _|| _|| _|| _|| _tt�| _d S )N� )�superr/ �__init__�_allowed_strategies�AssertionError�sysr r �_py_version_info�preparer�finder�session�require_hashes�upgrade_strategy�force_reinstall�ignore_dependencies�ignore_installedr) � use_user_site�_make_install_reqr �list�_discovered_dependencies) �selfr: r< r; Zmake_install_reqrB r@ rA r) r? r> Zpy_version_info�� __class__r, r- r5 u s& �zResolver.__init__c C s� | j jrt| j j� |jt|j�� � }|jp>tdd� |D ��| _| j j }|� � }|r`t � |� g }t� }t||�D ]N}z|�| �||�� W qt tk r� } z||_|�|� W 5 d}~X Y qtX qt|r�|�dS )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. c s s | ] }|j V qd S �N)Zhas_hash_options)�.0�reqr, r, r- � <genexpr>� s z#Resolver.resolve.<locals>.<genexpr>N)r: Zwheel_download_dirr Zunnamed_requirementsrD � requirements�valuesr= �anyr; � search_scopeZget_formatted_locationsr! �infor r �extend� _resolve_oner rK �append) rF �requirement_setZ root_reqsrP Z locationsZdiscovered_reqsZ hash_errorsrK r* r, r, r- �resolve� s2 ��� � zResolver.resolvec C s4 | j dkrdS | j dkr dS | j dks*t�|jS d S )Nr2 Fr0 Tr1 )r> r7 � is_direct�rF rK r, r, r- �_is_upgrade_allowed� s z Resolver._is_upgrade_allowedc C s, | j rt|j�r"t|j�r"|j|_d|_dS )z4 Set a requirement to be installed. N)rB r � satisfied_byr Zconflicts_withrX r, r, r- �_set_req_to_reinstall� s ��z Resolver._set_req_to_reinstallc C s� | j r dS |�| j� |js dS | jr4| �|� dS | �|�sP| jdkrLdS dS |js�z| j j |dd� W n( t k r� Y dS t k r� Y nX | �|� 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. Nr1 z#already satisfied, skipping upgradezalready satisfiedT)Zupgradezalready up-to-date) rA �check_if_existsrB rZ r? r[ rY r> �linkr; Zfind_requirementr r )rF �req_to_installr, r, r- �_check_skip_installed� s* z Resolver._check_skip_installedc C s� | j dk std��|jr0| j�|| j | j| j�S |jdks>t�| �|�}|jr`| j� || j |�S | � |�}|� | j|| j � | j� || j | j| j �}| js�|�| j� |jr�| jdkp�| jp�| jp�|jjdk}|r�| �|� n t�d|� |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()r2 �filez<Requirement already satisfied (use --upgrade to upgrade): %s)r= r7 �editabler: Z prepare_editable_requirementrB r; rZ r_ Z prepare_installed_requirementrY Z populate_linkZprepare_linked_requirementr< rA r\ r> r? r] Zschemer[ r! rQ )rF rK Z skip_reasonZupgrade_allowed� abstract_distZ should_modifyr, r, r- �_get_abstract_dist_for sV � � � � �� � �z Resolver._get_abstract_dist_forc s4 �j s �jrg S d�_�j��� ����}|�� }t|�j�jd� g � � ���fdd�}t � �� �� �j �s�d�_ �j �dd� �j�s �jr�t�dd��j�� tt�j�t|j� �}|D ]}t�d ||� q�tt|j�t�j�@ �}|�|�D ]} || |d � q��j�s&�j�s&�j��� W 5 Q R X � S ) zxPrepare a single requirements file. :return: A list of additional InstallRequirements to also install. T)r r) c sP �� t| ���}�j}�j|||d�\}}|rB|rB�j| �|� � �|� d S )N)�parent_req_name�extras_requested)rC r% �name�add_requirementrE rT rR )�subreqre Zsub_install_reqrd Z to_scan_againZ add_to_parent�Z more_reqsr^ rU rF r, r- �add_req} s �� �z&Resolver._resolve_one.<locals>.add_reqN)rd z!Installing extra requirements: %r�,z"%s does not provide the extra '%s')re )� constraintZpreparedZreqs_to_cleanuprT rc Z get_pkg_resources_distributionr. r9 r) r Zhas_requirementrf rW rg r@ Zextrasr! r& r# �sorted�setr" Zrequiresra rZ Zsuccessfully_downloaded) rF rU r^ rb r( rj Zmissing_requestedZmissingZavailable_requestedrh r, ri r- rS [ sV � � �� ��zResolver._resolve_onec s8 g � t � �� ���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. c sN | j s| �krd S | jr d S ��| � �j| j D ] }�|� q2� �| � d S rI )rZ rl �addrE rf rT )rK Zdep��orderZ ordered_reqs�schedulerF r, r- rr � s z1Resolver.get_installation_order.<locals>.schedule)rn rM rN )rF Zreq_setZ install_reqr, rp r- �get_installation_order� s z Resolver.get_installation_order)N)�__name__� __module__� __qualname__�__doc__r6 r5 rV rY r[ r_ rc rS rs � __classcell__r, r, rG r- r/ n s �+3 5<Zr/ )F)8rw Zloggingr8 � collectionsr � itertoolsr Zpip._vendor.packagingr Zpip._internal.exceptionsr r r r r Zpip._internal.utils.loggingr Zpip._internal.utils.miscr r r r Z pip._internal.utils.packagingr r Zpip._internal.utils.typingr �typingr r r r r r Z pip._vendorr Zpip._internal.distributionsr Z pip._internal.network.sessionr Zpip._internal.indexr Z pip._internal.operations.preparer Z pip._internal.req.req_installr Zpip._internal.req.req_setr r% ZInstallRequirementProviderZ getLoggerrt r! r. �objectr/ r, r, r, r- �<module> s4 � � 0