OwlCyberSecurity - MANAGER
Edit File: legacy_resolve.cpython-38.pyc
U �J)^�? � @ sB d Z ddlZddlZddlmZ ddlmZ ddlmZ ddl m Z m Z m Z m Z mZ ddlmZ ddlmZmZ dd lmZmZ dd lmZ e�rdd lmZmZm 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+ ee,e)ge)f Z-ee,e e) f Z.e�/e0�Z1ddd�Z2G dd� de3�Z4dS )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_usersite�normalize_version_info)�check_requires_python�get_requires_python)�MYPY_CHECK_RUNNING)�Callable� DefaultDict�List�Optional�Set�Tuple)� pkg_resources)�AbstractDistribution)� 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/dist-packages/pip/_internal/legacy_resolve.py�_check_dist_requires_python9 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| �} | | _|| _ || _ | | _ || _ || _ || _|| _|| _|| _tt�| _d S )N� )�superr, �__init__�_allowed_strategies�AssertionError�sysr r �_py_version_info�preparer�finder�upgrade_strategy�force_reinstall�ignore_dependencies�ignore_installedr& � use_user_site�_make_install_reqr �list�_discovered_dependencies) �selfr7 r8 Zmake_install_reqr= r; r< r& r: r9 Zpy_version_info�� __class__r) r* r2 p s" �zResolver.__init__c C s� |j t|j�� � }g }t� }t||�D ]N}z|�| �||�� W q( tk rt } z||_ |� |� W 5 d}~X Y q(X q(|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. N) Zunnamed_requirementsr? � requirements�valuesr r �extend� _resolve_oner �req�append)rA �requirement_setZ root_reqsZdiscovered_reqsZ hash_errorsrH r' r) r) r* �resolve� s �� zResolver.resolvec C s4 | j dkrdS | j dkr dS | j dks*t�|jS d S )Nr/ Fr- Tr. )r9 r4 � is_direct�rA rH r) r) r* �_is_upgrade_allowed� s z Resolver._is_upgrade_allowedc C s | j rt|j�rd|_d|_dS )z4 Set a requirement to be installed. TN)r= r � satisfied_byZshould_reinstallrM 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. Nr. z#already satisfied, skipping upgradezalready satisfiedT)Zupgradezalready up-to-date) r< �check_if_existsr= rO r: rP rN r9 �linkr8 Zfind_requirementr r )rA �req_to_installr) r) r* �_check_skip_installed� s* z Resolver._check_skip_installedc C s� |j r| j�|�S |jdks t�| �|�}|jr>| j�||�S | �|�}| jj}|� | j ||� | j� |�}| j s~|� | j� |jr�| jdkp�| jp�| j p�|jjdk}|r�| �|� n 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)�editabler7 Z prepare_editable_requirementrO r4 rT Z prepare_installed_requirementrN �require_hashesZ populate_linkr8 Zprepare_linked_requirementr< rQ r= r9 r: rR ZschemerP r �info)rA rH Z skip_reasonZupgrade_allowedrW � abstract_distZ should_modifyr) r) r* �_get_abstract_dist_for s< � �� � �z Resolver._get_abstract_dist_forc s8 �j s �jrg S d�_�j��� ����}|�� }t|�j�jd� g � � ���fdd�}t � �� �� �j �s��j szt ��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)r> r" �name�add_requirementr@ rI rF )�subreqr\ Zsub_install_reqr[ Z to_scan_againZ add_to_parent�Z more_reqsrS rJ rA r) r* �add_reqZ s �� �z&Resolver._resolve_one.<locals>.add_reqN)r[ z!Installing extra requirements: %r�,z"%s does not provide the extra '%s')r\ )� constraintZpreparedZreqs_to_cleanuprI rZ Z get_pkg_resources_distributionr+ r6 r& r Zhas_requirementr] rL r4 r^ r; Zextrasr r# r �sorted�setr ZrequiresrV rO Zsuccessfully_downloaded) rA rJ rS rY r% ra Zmissing_requestedZmissingZavailable_requestedr_ r) r` r* rG 8 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 )N)rO rc �addr@ r] rI )rH Zdep��orderZ ordered_reqs�schedulerA r) r* ri � s z1Resolver.get_installation_order.<locals>.schedule)re rD rE )rA Zreq_setZ install_reqr) rg r* �get_installation_order� s z Resolver.get_installation_order)N)�__name__� __module__� __qualname__�__doc__r3 r2 rK rN rP rT rZ rG rj � __classcell__r) r) rB r* r, i s �&# 55\r, )F)5rn Zloggingr5 � collectionsr � itertoolsr Zpip._vendor.packagingr Zpip._internal.exceptionsr r r r r Zpip._internal.utils.loggingr Zpip._internal.utils.miscr 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.index.package_finderr Z pip._internal.operations.preparer Z pip._internal.req.req_installr Zpip._internal.req.req_setr r" ZInstallRequirementProviderZDiscoveredDependenciesZ getLoggerrk r r+ �objectr, r) r) r) r* �<module> s4 � � 0