🔐 Sid Gifari File Manager Pro
v8.0.5 | 2026-06-14 17:08:39 | PHP 8.1.34
📂
/ (Root)
/
usr
/
lib
/
python3.9
/
site-packages
/
pip
/
_vendor
/
resolvelib
/
__pycache__
📍 /usr/lib/python3.9/site-packages/pip/_vendor/resolvelib/__pycache__
🔄 Refresh
✏️
Editing: providers.cpython-39.pyc
Read Only
a �lj� � @ s$ G d d� de �ZG dd� de �ZdS )c @ s8 e Zd ZdZdd� Zdd� Zdd� Zdd � Zd d � Zd S ) �AbstractProviderzADelegate class to provide requirement interface for the resolver.c C s t �dS )z�Given a requirement, return an identifier for it. This is used to identify a requirement, e.g. whether two requirements should have their specifier parts merged. N��NotImplementedError)�selfZrequirement_or_candidate� r �D/usr/lib/python3.9/site-packages/pip/_vendor/resolvelib/providers.py�identify s zAbstractProvider.identifyc C s t �dS )a� Produce a sort key for given requirement based on preference. The preference is defined as "I think this requirement should be resolved first". The lower the return value is, the more preferred this group of arguments is. :param identifier: An identifier as returned by ``identify()``. This identifies the dependency matches of which should be returned. :param resolutions: Mapping of candidates currently pinned by the resolver. Each key is an identifier, and the value a candidate. The candidate may conflict with requirements from ``information``. :param candidates: Mapping of each dependency's possible candidates. Each value is an iterator of candidates. :param information: Mapping of requirement information of each package. Each value is an iterator of *requirement information*. :param backtrack_causes: Sequence of requirement information that were the requirements that caused the resolver to most recently backtrack. A *requirement information* instance is a named tuple with two members: * ``requirement`` specifies a requirement contributing to the current list of candidates. * ``parent`` specifies the candidate that provides (dependend on) the requirement, or ``None`` to indicate a root requirement. The preference could depend on a various of issues, including (not necessarily in this order): * Is this package pinned in the current resolution result? * How relaxed is the requirement? Stricter ones should probably be worked on first? (I don't know, actually.) * How many possibilities are there to satisfy this requirement? Those with few left should likely be worked on first, I guess? * Are there any known conflicts for this requirement? We should probably work on those with the most known conflicts. A sortable value should be returned (this will be used as the ``key`` parameter of the built-in sorting function). The smaller the value is, the more preferred this requirement is (i.e. the sorting function is called with ``reverse=False``). Nr )r � identifierZ resolutionsZ candidatesZ informationZbacktrack_causesr r r �get_preference s 1z AbstractProvider.get_preferencec C s t �dS )a� Find all possible candidates that satisfy given constraints. :param identifier: An identifier as returned by ``identify()``. This identifies the dependency matches of which should be returned. :param requirements: A mapping of requirements that all returned candidates must satisfy. Each key is an identifier, and the value an iterator of requirements for that dependency. :param incompatibilities: A mapping of known incompatibilities of each dependency. Each key is an identifier, and the value an iterator of incompatibilities known to the resolver. All incompatibilities *must* be excluded from the return value. This should try to get candidates based on the requirements' types. For VCS, local, and archive requirements, the one-and-only match is returned, and for a "named" requirement, the index(es) should be consulted to find concrete candidates for this requirement. The return value should produce candidates ordered by preference; the most preferred candidate should come first. The return type may be one of the following: * A callable that returns an iterator that yields candidates. * An collection of candidates. * An iterable of candidates. This will be consumed immediately into a list of candidates. Nr )r r � requirementsZincompatibilitiesr r r � find_matches? s z AbstractProvider.find_matchesc C s t �dS )a Whether the given requirement can be satisfied by a candidate. The candidate is guarenteed to have been generated from the requirement. A boolean should be returned to indicate whether ``candidate`` is a viable solution to the requirement. Nr )r Z requirement� candidater r r �is_satisfied_by\ s z AbstractProvider.is_satisfied_byc C s t �dS )z�Get dependencies of a candidate. This should return a collection of requirements that `candidate` specifies as its dependencies. Nr )r r r r r �get_dependenciesg s z!AbstractProvider.get_dependenciesN) �__name__� __module__� __qualname__�__doc__r r r r r r r r r r s 3 r c @ s$ e Zd ZdZeZdd� Zdd� ZdS )�AbstractResolverz3The thing that performs the actual resolution work.c C s || _ || _d S )N)�provider�reporter)r r r r r r �__init__u s zAbstractResolver.__init__c K s t �dS )a� Take a collection of constraints, spit out the resolution result. This returns a representation of the final resolution state, with one guarenteed attribute ``mapping`` that contains resolved candidates as values. The keys are their respective identifiers. :param requirements: A collection of constraints. :param kwargs: Additional keyword arguments that subclasses may accept. :raises: ``self.base_exception`` or its subclass. Nr )r r �kwargsr r r �resolvey s zAbstractResolver.resolveN)r r r r � ExceptionZbase_exceptionr r r r r r r p s r N)�objectr r r r r r �<module> s o
💾 Save Changes
❌ Cancel