/usr/local/lib/python3.9/site-packages/pip/_internal/resolution/legacy/__pycache__
a ���h�] � @ s� d Z ddlmZ ddlZddlZddlmZ ddlmZ ddl m Z ddl m Z ddl mZ dd lmZ dd lmZ dd lmZmZmZmZmZmZmZ dd lm Z dd l m Z ddl m Z ddl!m"Z" ddl#m$Z$ ddl%m&Z&m'Z' ddl(m)Z) ddl*m+Z+m,Z, ddl-m.Z. ddl/m0Z0 ddl1m2Z2 ddl3m4Z4 ddl5m6Z6 ddl7m8Z8 e�9e:�Z;ee e< e=e& f Z>d$dd d d d �d d!�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) � )� annotationsN)� defaultdict)�Iterable)�chain)�Optional)� specifiers)� Requirement)� WheelCache)�BestVersionAlreadyInstalled�DistributionNotFound� HashError� HashErrors�InstallationError�NoneMetadataError�UnsupportedPythonVersion)� PackageFinder)�BaseDistribution)�Link)�Wheel)�RequirementPreparer)�InstallRequirement� check_invalid_constraint_type)�RequirementSet)� BaseResolver�InstallRequirementProvider)�compatibility_tags)� get_supported)�direct_url_from_link)� indent_log)�normalize_version_info)�check_requires_pythonFr ztuple[int, int, int]�bool�None)�dist� version_info�ignore_requires_python�returnc C s� zt | j�}W n2 ty@ } zt| t |���W Y d}~n d}~0 0 zt||d�}W n8 tjy� } z t�d| j |� W Y d}~dS d}~0 0 |r�dS d� t t |��}|r�t� d| j ||� dS t 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 )�str�requires_python�FileNotFoundErrorr r r �InvalidSpecifier�logger�warning�raw_name�join�map�debugr )r# r$ r% r) �e� is_compatible�exc�version� r6 �R/usr/local/lib/python3.9/site-packages/pip/_internal/resolution/legacy/resolver.py�_check_dist_requires_python: s@ $� �� ���r8 c s� e Zd ZdZh d�Zd1dddddddddd d d d � � fd d� Zdddd�dd�Zd2dddddd�dd�Zddd�d d �Zdd d�d d �Z ddd �d!d"�Z dd#d�d$d%�Z dd d�d&d'�Z dd(d�d)d*�Z dddd+�d,d-�Zddd.�d/d0�Z� ZS )3�Resolverz�Resolves which packages need to be installed/uninstalled to perform the requested operation without breaking the requirements of any package. > �only-if-needed�to-satisfy-only�eagerNr r zWheelCache | Noner r! r( ztuple[int, ...] | Noner" ) �preparer�finder� wheel_cache�make_install_req� use_user_site�ignore_dependencies�ignore_installedr% �force_reinstall�upgrade_strategy�py_version_infor& c s� t � �� | | jv sJ �| d u r0tjd 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 w s" zResolver.__init__zlist[InstallRequirement]r )� root_reqs�check_supported_wheelsr& c C s� t |d�}|D ] }|jr t|� | �||� qg }t� }t|j|�D ]P}z|�| �||�� W qD t y� } z ||_ |� |� W Y d}~qDd}~0 0 qD|r�|�|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_requirement_to_setr r �all_requirements�extend� _resolve_oner �req�append)rP rS rT �requirement_setrZ Zdiscovered_reqsZ hash_errorsr4 r6 r6 r7 �resolve� s "zResolver.resolver z str | NonezIterable[str] | Nonez:tuple[list[InstallRequirement], InstallRequirement | None])r\ � install_req�parent_req_name�extras_requestedr& c C s� |� |�s$t�d|j|j� g dfS |jrf|jjrft|jj�}t � � }|j rf|� |�sft |j� d���|jr||du s|J d��|js�|�|� |gdfS z|�|j�}W n ty� d}Y n0 |du o�|o�|j o�|j|jko�|jo�|jo�|jj|jjk}|�r t d|� d|� d|j�d���|�s8|�|� |g|fS |j�sH|j�sPg |fS |j�op|j�on|jj|jjk } | �r�t d |j� d ���d |_|j�r�d |_ttt|j�t|j�B ��|_t�d ||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, �info�name�markers�link�is_wheelr �filenamer r rT � supportedr � user_supplied�add_unnamed_requirement�get_requirement�KeyErrorrU �extrasrZ � specifier�add_named_requirement�path�tuple�sorted�setr1 ) rP r\ r^ r_ r` �wheel�tags� existing_req�has_conflicting_requirement�does_not_satisfy_constraintr6 r6 r7 rV � s� � ���� � �� ���� ��� � ���z Resolver._add_requirement_to_set�rZ r& c C s: | j dkrdS | j dkr dS | j dks*J �|jp4|jS d S )Nr; Fr< Tr: )rE rj rU �rP rZ r6 r6 r7 �_is_upgrade_allowed5 s z Resolver._is_upgrade_allowedc C s, |j dusJ �| jr |j jr"d|_d|_ dS )z4 Set a requirement to be installed. NT)� satisfied_byrA � in_usersite�should_reinstallr{ r6 r6 r7 �_set_req_to_reinstall> s z Resolver._set_req_to_reinstall)�req_to_installr& c C s� | j r dS |�| j� |js dS | jr4| �|� dS | �|�sP| jdkrLdS dS |js�z| j j |dd� W n$ t y~ Y dS t y� Y n0 | �|� 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 r} rD r� r| rE rf r> �find_requirementr r )rP r� r6 r6 r7 �_check_skip_installedI s* z Resolver._check_skip_installedz Link | Nonec C sT | � |�}| j�||�}|s d S |j}|jrP|jp4d}d|� d|� �}t�|� |S )Nz <none given>zDThe candidate selected for download or install is a yanked version: z Reason for being yanked: )r| r> r� rf � is_yanked� yanked_reasonr, r- )rP rZ r� �best_candidaterf �reason�msgr6 r6 r7 �_find_requirement_link} s ��� z Resolver._find_requirement_linkc C s� |j du r| �|�|_ | jdu s(| jjr,dS |j dus>J d��| jj|j |jt� d�}|dur�t� d|j � |j |j u r�|j r�|j |_ |j dur�|j |_nt|j |j d�|_|j |_ 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. Nz1_find_requirement_link unexpectedly returned None)rf � package_name�supported_tagszUsing cached wheel link: %s)�link_is_in_wheel_cache)rf r� r? r= �require_hashes�get_cache_entryrd r r, r1 � original_link� persistentZcached_wheel_source_link�originZ download_infor )rP rZ � cache_entryr6 r6 r7 �_populate_link� s( � �zResolver._populate_linkr c C s� |j r| j�|�S |jdu s J �| �|�}|jr>| j�||�S | �|� | j�|�}| jsf|� | j � |jr�| j dkp�| j p�| jp�|j jdk}|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)�editabler= � prepare_editable_requirementr} r� � prepare_installed_requirementr� �prepare_linked_requirementrC r� rA rE rD rf �schemer� r, rc )rP rZ � skip_reasonr# Z should_modifyr6 r6 r7 � _get_dist_for� s2 �� � �zResolver._get_dist_for)r\ r� r& c sD �j s �jrg S d�_����}t|�j�jd� g � dddd�� ���fdd� }t� �� �jd ushJ ����j�s��j s~J ��j ��d d � �j �s �j r�t �d d ��j �� tt�j �t|�� � �}|D ]}t �d |j|j|� q�tt|�� �t�j �@ �}|�|�D ]}|||d� �q W d � n1 �s60 Y � S )zxPrepare a single requirements file. :return: A list of additional InstallRequirements to also install. T)r$ r% r z Iterable[str]r" )�subreqr` r& c sR �� t| ���}�j}�j�|||d�\}}|rD|rD�j| �|� � �|� d S )N)r_ r` )rM r( rd rV rO r[ rX )r� r` Zsub_install_reqr_ Z to_scan_againZ add_to_parent�Z more_reqsr� r\ rP r6 r7 �add_req s � z&Resolver._resolve_one.<locals>.add_reqN)r_ z!Installing extra requirements: %r�,z%%s %s does not provide the extra '%s')r` )rU �preparedr� r8 rL r% r rd �has_requirementrj rV rB rn r, r1 r/ rs rt �iter_provided_extrasr- r. r5 �iter_dependencies) rP r\ r� r# r� Zmissing_requested�missingZavailable_requestedr� r6 r� r7 rY � sP � � ����0zResolver._resolve_one)�req_setr& c s@ g � t � �ddd�� ���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. r r" rz c sN | j s| �v rd S | jr d S ��| � �j| j D ] }�|� q2� �| � d S )N)r} rU �addrO rd r[ )rZ �dep��orderZ ordered_reqs�schedulerP r6 r7 r� J s z1Resolver.get_installation_order.<locals>.schedule)rt � requirements�values)rP r� r^ r6 r� r7 �get_installation_order; s z Resolver.get_installation_order)N)NN)�__name__� __module__� __qualname__�__doc__rJ rI r] rV r| r� r� r� r� r� rY r� � __classcell__r6 r6 rQ r7 r9 p s �*&) �s 4'.Sr9 )F)Ar� � __future__r �loggingrK � collectionsr �collections.abcr � itertoolsr �typingr Zpip._vendor.packagingr Z"pip._vendor.packaging.requirementsr �pip._internal.cacher �pip._internal.exceptionsr r r r r r r �"pip._internal.index.package_finderr �pip._internal.metadatar �pip._internal.models.linkr �pip._internal.models.wheelr � pip._internal.operations.preparer Z pip._internal.req.req_installr r Zpip._internal.req.req_setr � pip._internal.resolution.baser r Zpip._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 � getLoggerr� r, r( rN ZDiscoveredDependenciesr8 r9 r6 r6 r6 r7 �<module> s< $ �6
.
Edit
..
Edit
__init__.cpython-39.pyc
Edit
resolver.cpython-39.pyc
Edit