Файловый менеджер - Редактировать - /usr/lib/python3/dist-packages/pip/_internal/resolution/resolvelib/__pycache__/provider.cpython-310.pyc
Ðазад
o !��h�& � @ s� d dl Z d dlZd dlmZmZmZmZmZmZm Z m Z d dl m Z ddl mZmZmZ ddlmZ ddlmZ erTd dl mZ d d lmZ eeef Ze eeef Zne Ze d �Ze d �Z d eee f d edede ee f fdd�Z G dd� de�Z dS )� N)� TYPE_CHECKING�Dict�Iterable�Iterator�Mapping�Sequence�TypeVar�Union)�AbstractProvider� )� Candidate� Constraint� Requirement)�REQUIRES_PYTHON_IDENTIFIER)�Factory)� Preference)�RequirementInformation�D�V�mapping� identifier�default�returnc C s8 || v r| | S |� d�\}}}|r|| v r| | S |S )ai Get item from a package name lookup mapping with a resolver identifier. This extra logic is needed when the target mapping is keyed by package name, which cannot be directly looked up with an identifier (which may contain requested extras). Additional logic is added to also look up a value by "cleaning up" the extras from the identifier. �[)� partition)r r r �name� open_bracket�_� r �N/usr/lib/python3/dist-packages/pip/_internal/resolution/resolvelib/provider.py�_get_with_identifier5 s r c @ s" e Zd ZdZdedeeef dededeee f ddf d d �Z d e e e f defd d �Zdedeee f deeee f deeed f ded ddf dd�Zdedeeee f deeee f dee fdd�Zde d e defd d �Zd e dee fd d �Zededed defd!d"��ZdS )#� PipProvidera� Pip's provider implementation for resolvelib. :params constraints: A mapping of constraints specified by the user. Keys are canonicalized project names. :params ignore_dependencies: Whether the user specified ``--no-deps``. :params upgrade_strategy: The user-specified upgrade strategy. :params user_requested: A set of canonicalized package names that the user supplied for pip to install/upgrade. �factory� constraints�ignore_dependencies�upgrade_strategy�user_requestedr Nc C s2 || _ || _|| _|| _|| _t�dd� �| _d S )Nc S s t jS �N)�math�infr r r r �<lambda>f s z&PipProvider.__init__.<locals>.<lambda>)�_factory� _constraints�_ignore_dependencies�_upgrade_strategy�_user_requested� collections� defaultdict� _known_depths)�selfr" r# r$ r% r& r r r �__init__Y s zPipProvider.__init__�requirement_or_candidatec C s |j S r' )r )r3 r5 r r r �identifyh s zPipProvider.identifyr � resolutions� candidates� information�PreferenceInformation�backtrack_causesr c s dd� || D �}t |� \}}dd� dd� |D �D �} |du} tdd� | D ��} t| �} z� j| } W n" tyU tj} � fdd�|| D �}td d� |D ��d }Y nw d }|� j|< � j� |tj�} |t k}|d k}� � ||�}| || | | || | |f S ) a[ Produce a sort key for given requirement based on preference. The lower the return value is, the more preferred this group of arguments is. Currently pip considers the followings in order: * Prefer if any of the known requirements is "direct", e.g. points to an explicit URL. * If equal, prefer if any requirement is "pinned", i.e. contains operator ``===`` or ``==``. * If equal, calculate an approximate "depth" and resolve requirements closer to the user-specified requirements first. * Order user-specified requirements by the order they are specified. * If equal, prefers "non-free" requirements, i.e. contains at least one operator, such as ``>=`` or ``<``. * If equal, order alphabetically for consistency (helps debuggability). c s s � | ] \}}|� � V qd S r' )�get_candidate_lookup)�.0�rr r r r � <genexpr>� s � z-PipProvider.get_preference.<locals>.<genexpr>c S s g | ] }|D ]}|j �qqS r )�operator)r= � specifier_set� specifierr r r � <listcomp>� s ���z.PipProvider.get_preference.<locals>.<listcomp>c s s � | ]}|r|j V qd S r' )rB )r= �ireqr r r r? � s � Nc s s � | ] }|d d� dkV qd S )N� z==r )r= �opr r r r? � s � c 3 s, � | ]\}}|d ur� j |j ndV qd S )Ng )r2 r )r= r �parent�r3 r r r? � s � � �c s s � | ]}|V qd S r' r )r= �dr r r r? � s � g �?� setuptools) �zip�any�boolr/ �KeyErrorr( r) �minr2 �getr �is_backtrack_cause)r3 r r7 r8 r9 r; �lookups� candidate�ireqs� operators�direct�pinned�unfree�requested_order� parent_depths�inferred_depth�requires_python� delay_this�backtrack_causer rH r �get_preferencek sB � �� �zPipProvider.get_preference� requirements�incompatibilitiesc sF dt dtf� fdd� }t� j|t�� d�}� jj|||||� |d�S )Nr r c s4 � j dkrdS � j dkrt� j| dd�}|duS dS )a� Are upgrades allowed for this project? This checks the upgrade strategy, and whether the project was one that the user specified in the command line, in order to decide whether we should upgrade if there's a newer version available. (Note that we don't need access to the `--upgrade` flag, because an upgrade strategy of "to-satisfy-only" means that `--upgrade` was not specified). �eagerTzonly-if-neededN�r F)r. r r/ )r � user_orderrH r r �_eligible_for_upgrade� s �z7PipProvider.find_matches.<locals>._eligible_for_upgraderc )r r` � constraint�prefers_installedra )�strrM r r, r �emptyr+ �find_candidates)r3 r r` ra re rf r rH r � find_matches� s ��zPipProvider.find_matches� requirementrS c C s |� |�S r' )�is_satisfied_by)r3 rl rS r r r rm � s zPipProvider.is_satisfied_byc C s | j }dd� |�|�D �S )Nc S s g | ]}|d ur|�qS r' r )r= r> r r r rC � s z0PipProvider.get_dependencies.<locals>.<listcomp>)r- �iter_dependencies)r3 rS � with_requiresr r r �get_dependencies� s z PipProvider.get_dependenciesc C s8 |D ]}| |j jkr dS |jr| |jjkr dS qdS )NTF)rl r rG )r r; r^ r r r rQ � s �z PipProvider.is_backtrack_cause)�__name__� __module__� __qualname__�__doc__r r rh r rM �intr4 r r r r6 r r r r r_ rk rm rp � staticmethodrQ r r r r r! N s` � ��� � �� ���� �T��� �)���r! ) r0 r( �typingr r r r r r r r � pip._vendor.resolvelib.providersr �baser r r r8 r r" r r � pip._vendor.resolvelib.resolversr r: rh � _ProviderBaser r r r! r r r r �<module> s2 ( ��� �
| ver. 1.1 | |
.
| PHP 8.4.18 | Ð“ÐµÐ½ÐµÑ€Ð°Ñ†Ð¸Ñ Ñтраницы: 0 |
proxy
|
phpinfo
|
ÐаÑтройка