a
ljH @ sz d Z ddlZddlZddlmZ ddlmZ ddlmZm Z m
Z
m Z m Z m
Z
ddlmZ ddlmZ ddlmZ dd lmZmZmZmZmZmZ dd
lm Z dd l m Z dd l m Z dd
l!m"Z" ddl#m$Z$m%Z% ddl&m'Z' ddl(m)Z)m*Z* ddl+m,Z, ddl-m.Z. ddl/m0Z0m1Z1 ddl/m2Z2 ddl3m4Z4 e5e6Z7ee8e
e$ f Z9d e e
e:e:e:f e;ddddZ to-satisfy-onlyonly-if-neededeagerN.) preparerfinder wheel_cachemake_install_req
use_user_siteignore_dependenciesignore_installedr$ force_reinstallupgrade_strategypy_version_infor% c sz t | d u r"tjd d } nt| } | | _|| _|| _|| _|
| _ | | _
|| _ || _ || _
|| _|| _tt| _d S )N )super__init__sysr# r _py_version_infor; r< r= rC rB r@ rA r$ r? _make_install_reqr list_discovered_dependencies) selfr; r< r= r> r? r@ rA r$ rB rC rD __class__r4 r5 rG u s
zResolver.__init__) root_reqscheck_supported_wheelsr% c C s t |d}|D ] }|jr t| || qg }t }t|j|D ]P}z|| || W qB t y } z ||_
| | W Y d}~qBd}~0 0 qB|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.
)rQ N) r
constraintr add_requirementr r Zall_requirementsextend _resolve_oner reqappend)rM rP rQ requirement_setrV Zdiscovered_reqsZ hash_errorsr2 r4 r4 r5 resolve s
"zResolver.resolverV r% c C s, | j dkrdS | j dkr dS |jp&|jS d S )Nr8 Fr: T)rC Z
user_suppliedrR rM rV r4 r4 r5 _is_upgrade_allowed s
z Resolver._is_upgrade_allowedc C s* | j rt|jr t|jr d|_d|_dS )z4
Set a requirement to be installed.
TN)r? r satisfied_byr Zshould_reinstallr[ r4 r4 r5 _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 |jsz| 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.
Nr9 z#already satisfied, skipping upgradezalready satisfiedT)upgradezalready up-to-date)
rA check_if_existsr? r] rB r^ r\ rC linkr< find_requirementr
r )rM r_ r4 r4 r5 _check_skip_installed s*
z Resolver._check_skip_installedc C sR | |}| j||}|s d S |j}|jrN|jp4d}dj||d}t| |S )Nz zqThe candidate selected for download or install is a yanked version: {candidate}
Reason for being yanked: {reason}) candidatereason) r\ r< rc rb Z is_yankedZ
yanked_reasonr0 r* r+ )rM rV r` Zbest_candidaterb rf msgr4 r4 r5 _find_requirement_link s
z Resolver._find_requirement_linkc C s~ |j du r| ||_ | jdu s(| jjr,dS | jj|j |jt d}|durzt d|j |j |j
u rr|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 Z package_nameZsupported_tagszUsing cached wheel link: %sT)
rb rh r= r; Zrequire_hashesZget_cache_entrynamer r* r/ Z
original_linkZ
persistentZ original_link_is_in_wheel_cache)rM rV Z cache_entryr4 r4 r5 _populate_link! s
zResolver._populate_linkc C s |j r| j|S | |}|jr0| j||S | | | j|}| jsX| | j
|jr| j dkp~| j p~| jp~|j
jdk}|r| | n td| |S )zzTakes a InstallRequirement and returns a single AbstractDist representing a prepared variant of the same.
r8 filez s0
zResolver._get_dist_for)rX r_ r% c s, j s jrg S d_}t|jjd g ttt dd fdd }t
j sxj dd j
sjrtdd j ttjt| }|D ]}td
|j|j| qtt| tj@ }||D ]}|||d qW d n1 s 0 Y S ) zxPrepare a single requirements file.
:return: A list of additional InstallRequirements to also install.
T)r# r$ N)subreqextras_requestedr% c sP t| }j}j|||d\}}|rB|rBj| | | d S )N)parent_req_namerp )rJ r' ri rS rL rW rT )ro rp Zsub_install_reqrq Z
to_scan_againZ
add_to_parentZ more_reqsr_ rX rM r4 r5 add_req s
z&Resolver._resolve_one..add_req)rq z!Installing extra requirements: %r,z%%s %s does not provide the extra '%s')rp )rR Zpreparedrn r6 rI r$ r r r' r Zhas_requirementri rS r@ extrasr* r/ r- sortedsetZiter_provided_extrasr+ r, r3 Ziter_dependencies) rM rX r_ r" rs Zmissing_requestedmissingZavailable_requestedro r4 rr r5 rU l sH
.zResolver._resolve_one)req_setr% c s@ g t tdd fdd |j D ] }| q. S )zCreate 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.
NrZ c sN | j s| v rd S | jr d S | j| j D ] }| q2 | d S )N)r] rR addrL ri rW )rV ZdeporderZ ordered_reqsschedulerM r4 r5 r} s
z1Resolver.get_installation_order..schedule)rw r Z requirementsvalues)rM ry Z install_reqr4 r{ r5 get_installation_order s
z Resolver.get_installation_order)N) __name__
__module__ __qualname____doc__Z_allowed_strategiesr r r r r boolr' r intrG r r r rY r\ r^ rd r rh rj r rn rU r
__classcell__r4 r4 rN r5 r7 n sF ' %
6 0 Pr7 )F)>r ZloggingrH collectionsr itertoolsr typingr r r r r r Zpip._vendor.packagingr
Z"pip._vendor.packaging.requirementsr Zpip._internal.cacher Zpip._internal.exceptionsr
r r r r r Z"pip._internal.index.package_finderr Zpip._internal.metadatar Zpip._internal.models.linkr Z pip._internal.operations.preparer Z pip._internal.req.req_installr r Zpip._internal.req.req_setr Z pip._internal.resolution.baser r Z&pip._internal.utils.compatibility_tagsr Zpip._internal.utils.loggingr Zpip._internal.utils.miscr r r Z pip._internal.utils.packagingr! Z getLoggerr r* r' ZDiscoveredDependenciesr r r6 r7 r4 r4 r4 r5 s>
7