📁 File Manager Pro
v10.0.2 | PHP: 8.1.34
Server: LiteSpeed
2026-06-27 17:58:19
📂
/
/
opt
/
alt
/
python36
/
lib
/
python3.6
/
site-packages
/
pip
/
_internal
/
resolution
/
legacy
/
__pycache__
✏️
Editing: resolver.cpython-36.pyc
3 �Re�I � @ s� d Z ddlZddlZddlmZ ddlmZ ddlmZ ddl m Z m Z m Z m Z mZ ddlmZ ddlmZ dd lmZ dd lmZ dd lmZ dd lmZmZ dd lm Z ddl m Z m Z ddl m!Z! e!�rZddl"m#Z#m$Z$m%Z%m&Z&m'Z' ddl(m)Z) ddl*m+Z+ ddl,m-Z- ddl.m/Z/ ddl0m1Z1 ddl2m3Z3 ddlm4Z4 ddlm5Z5 e#e6e$e4 f Z7ej8e9�Z:d dd�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)� specifiers)�BestVersionAlreadyInstalled�DistributionNotFound� HashError� HashErrors�UnsupportedPythonVersion)� check_invalid_constraint_type)�RequirementSet)� BaseResolver)� get_supported)� indent_log)�dist_in_usersite�normalize_version_info)�dist_in_install_path)�check_requires_python�get_requires_python)�MYPY_CHECK_RUNNING)� DefaultDict�List�Optional�Set�Tuple)� pkg_resources)� WheelCache)�AbstractDistribution)� PackageFinder)�Link)�RequirementPreparer)�InstallRequirement)�InstallRequirementProviderFc C s� t | �}yt||d�}W n2 tjk rJ } ztjd| j|� dS d}~X nX |rTdS djtt |��}|r~tj d| j||� dS t dj | 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 �InvalidSpecifier�logger�warning� project_name�join�map�str�debugr �format)�distr" �ignore_requires_python�requires_python� is_compatible�exc�version� r3 ��/builddir/build/BUILDROOT/alt-python36-pip-20.2.4-5.el8.x86_64/opt/alt/python36/lib/python3.6/site-packages/pip/_internal/resolution/legacy/resolver.py�_check_dist_requires_python= s( r5 c st e Zd ZdZdddhZd� fdd� Zdd � Zd d � Zd d � Zdd� Z dd� Z dd� Z dd� Z dd� Z dd� Z� ZS )�Resolverz�Resolves which packages need to be installed/uninstalled to perform the requested operation without breaking the requirements of any package. �eagerzonly-if-neededzto-satisfy-onlyNc s� t t| �j� | | jks t�| d kr4tjd d� } nt| �} | | _|| _ || _ || _ | | _ | | _ || _|| _|| _|| _|| _tt�| _d S )N� )�superr6 �__init__�_allowed_strategies�AssertionError�sysr" r �_py_version_info�preparer�finder� wheel_cache�upgrade_strategy�force_reinstall�ignore_dependencies�ignore_installedr. � use_user_site�_make_install_reqr �list�_discovered_dependencies) �selfr? r@ rA �make_install_reqrF rD rE r. rC rB �py_version_info)� __class__r3 r4 r: t s" zResolver.__init__c C s� t |d�}x$|D ] }|jr"t|� |j|� qW g }t� }x^t|j|�D ]N}y|j| j||�� W qH t k r� } z||_ |j |� W Y dd}~X qHX qHW |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. )�check_supported_wheelsN) r � constraintr �add_requirementr r �all_requirements�extend� _resolve_oner �req�append)rJ � root_reqsrN �requirement_setrT �discovered_reqs� hash_errorsr1 r3 r3 r4 �resolve� s" zResolver.resolvec C s: | j dkrdS | j dkr dS | j dks*t�|jp4|jS d S )Nzto-satisfy-onlyFr7 Tzonly-if-needed)rB r< � user_suppliedrO )rJ rT r3 r3 r4 �_is_upgrade_allowed� s z Resolver._is_upgrade_allowedc C s, | j st|j�r"t|j�r"d|_d|_dS )z4 Set a requirement to be installed. TN)rF r � satisfied_byr �should_reinstall)rJ rT r3 r3 r4 �_set_req_to_reinstall� s z Resolver._set_req_to_reinstallc C s� | j r dS |j| j� |js dS | jr4| j|� dS | j|�sP| jdkrLdS dS |js�y| j j |dd� W n& t k r~ dS t k r� Y nX | j|� 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. Nzonly-if-neededz#already satisfied, skipping upgradezalready satisfiedT)�upgradezalready up-to-date) rE �check_if_existsrF r] rC r_ r\ rB �linkr@ �find_requirementr r )rJ �req_to_installr3 r3 r4 �_check_skip_installed� s* z Resolver._check_skip_installedc C sR | j |�}| jj||�}|s d S |j}|jrN|jp4d}dj||d�}tj|� |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@ rc rb � is_yanked� yanked_reasonr, r% r& )rJ rT r` �best_candidaterb rg �msgr3 r3 r4 �_find_requirement_link s z Resolver._find_requirement_linkc C s~ |j dkr| j|�|_ | jdks(| jjr,dS | jj|j |jt� d�}|dk rztj d|j � |j |j krr|j rrd|_ |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. N)rb � package_name�supported_tagszUsing cached wheel link: %sT) rb rl rA r? �require_hashes�get_cache_entry�namer r% r+ � original_link� persistent� original_link_is_in_wheel_cache)rJ rT � cache_entryr3 r3 r4 �_populate_link% s zResolver._populate_linkc C s� |j r| jj|�S |jdks t�| j|�}|jr>| jj||�S | j|� | jj|�}| j sf|j | j � |jr�| j dkp�| j p�| j p�|jjdk}|r�| j|� n tjd|� |S )zzTakes a InstallRequirement and returns a single AbstractDist representing a prepared variant of the same. Nzto-satisfy-only�filez<Requirement already satisfied (use --upgrade to upgrade): %s)�editabler? � prepare_editable_requirementr] r< re � prepare_installed_requirementrv �prepare_linked_requirementrE ra rF rB rC rb �schemer_ r% �info)rJ rT � skip_reason� abstract_dist� should_modifyr3 r3 r4 �_get_abstract_dist_forC s, z Resolver._get_abstract_dist_forc s2 �j s �jrg S d�_�j��}|j� }t|�j�jd� g � � ���fdd�}t� �� �j�j �s|�j snt ��j �dd� �j �s �jr�tjddj�j�� tt�j�t|j� �}x|D ]}tjd ||� q�W tt|j�t�j�@ �}x |j|�D ]} || |d � q�W �j �r$�j �r$d�_W dQ R X � S ) zxPrepare a single requirements file. :return: A list of additional InstallRequirements to also install. T)r" r. c sP �j t| ���}�j}�j|||d�\}}|rB|rB�j| j|� � j|� d S )N)�parent_req_name�extras_requested)rG r* rq rP rI rU rR )�subreqr� �sub_install_reqr� � to_scan_again� add_to_parent)� more_reqsrd rW rJ r3 r4 �add_req� s z&Resolver._resolve_one.<locals>.add_reqN)r� z!Installing extra requirements: %r�,z"%s does not provide the extra '%s')r� )rO �preparedr� � get_pkg_resources_distributionr5 r> r. r �has_requirementrq r[ r< rP rD �extrasr% r+ r( �sorted�setr& �requiresrx r] �successfully_downloaded) rJ rW rd r r- r� �missing_requested�missing�available_requestedr� r3 )r� rd rW rJ r4 rS u sB zResolver._resolve_onec s< g � t � �� ���fdd��x|jj� D ] }�|� q(W � 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 sR | j s| �krd S | jr d S �j| � x �j| j D ] }�|� q4W � j| � d S )N)r] rO �addrI rq rU )rT �dep)�order� ordered_reqs�schedulerJ r3 r4 r� � s z1Resolver.get_installation_order.<locals>.schedule)r� � requirements�values)rJ �req_set� install_reqr3 )r� r� r� rJ r4 �get_installation_order� s z Resolver.get_installation_order)N)�__name__� __module__� __qualname__�__doc__r; r: rZ r\ r_ re rl rv r� rS r� � __classcell__r3 r3 )rM r4 r6 m s & 5 2Yr6 )F)=r� �loggingr= � collectionsr � itertoolsr Zpip._vendor.packagingr �pip._internal.exceptionsr r r r r Z pip._internal.req.req_installr Zpip._internal.req.req_setr � pip._internal.resolution.baser �&pip._internal.utils.compatibility_tagsr �pip._internal.utils.loggingr �pip._internal.utils.miscr r r � pip._internal.utils.packagingr r �pip._internal.utils.typingr �typingr r r r r � pip._vendorr �pip._internal.cacher �pip._internal.distributionsr �"pip._internal.index.package_finderr �pip._internal.models.linkr � pip._internal.operations.preparer r r! r* ZDiscoveredDependencies� getLoggerr� r% r5 r6 r3 r3 r3 r4 �<module> s: -
💾 Save Changes
❌ Cancel