U
ʗReQ @ s d Z ddlZddlZddlmZmZmZ ddlmZm Z m
Z
m Z m Z ddl
mZmZ ddlmZmZmZ ddlmZ ddlmZ erdd lmZ dd
lmZ dd lm Z dd l m Z e e d
ddZ!e ee f ee e edddZ"G dd de#Z$G dd de$Z%G dd de$Z&G dd de$Z'G dd d e$Z(G d d d e%Z)G d d d e%Z*G d!d" d"e$Z+G d#d$ d$e'Z,G d%d& d&e'Z-G d'd( d(e'Z.G d)d* d*e'Z/G d+d, d,e$Z0G d-d. d.e$Z1G d/d0 d0e$Z2G d1d2 d2e$Z3G d3d4 d4e$Z4G d5d6 d6e'Z5G d7d8 d8e'Z6G d9d: d:e'Z7G d;d< d d>e%Z9G d?d@ d@e%e'Z:G dAdB dBe:e'Z;G dCdD dDe'ZG dIdJ dJe=Z?G dKdL dLe=Z@G dMdN dNe=ZAG dOdP dPe=ZBG dQdR dRe'ZCG dSdT dTe&ZDdS )UzExceptions used throughout package.
This module MUST NOT try to import from anything within `pip._internal` to
operate. This is expected to be importable from any/all files within the
subpackage and, thus, should not depend on them.
N)chaingroupbyrepeat)
TYPE_CHECKINGDictListOptionalUnion)RequestResponse)ConsoleConsoleOptions RenderResult)escape)Text)_Hash)Literal)BaseDistribution)InstallRequirement)sreturnc C s t d| d k S )Nz^[a-z]+(-[a-z]+)*$)rematch)r r /builddir/build/BUILDROOT/alt-python38-pip-22.2.1-2.el8.x86_64/opt/alt/python38/lib/python3.8/site-packages/pip/_internal/exceptions.py_is_kebab_case s r )r consoleprefixindentr c C sJ t | tr| }n
|| }|j|dd|jd| dd|jdd S )Nignore)overflow
T) allow_blank)
isinstancer
render_strjoinsplit)r r r r textr r r _prefix_with_indent! s
r( c @ s e Zd ZdZdS )PipErrorzThe base pip error.N__name__
__module__ __qualname____doc__r r r r r) 2 s r) c
s e Zd ZU dZeed< ddddddee eeef eeeef eeeef eeeef ee dd fdd Z ed
d d Z
e e e
d
ddZ ZS )DiagnosticPipErrora An error, that presents diagnostic information to the user.
This contains a bunch of logic, to enable pretty presentation of our error
messages. Each error gets a unique reference. Each error can also include
additional context, a hint and/or a note -- which are presented with the
main error message in a consistent style.
This is adapted from the error output styling in `sphinx-theme-builder`.
referenceerrorN)kindr0 note_stmtlinkzLiteral["error", "warning"])r2 r0 messagecontext hint_stmtr3 r4 r c s~ |d kr t | dstd| j}t|s0td|| _|| _|| _|| _|| _|| _|| _ t
d| j j
d| j d d S )Nr0 z error reference not provided!z#error reference must be kebab-case!)hasattrAssertionErrorr0 r r2 r5 r6 r3 r7 r4 super__init__ __class__r+ )selfr2 r0 r5 r6 r7 r3 r4 r> r r r= C s zDiagnosticPipError.__init__r c
C s8 d| j j d| jd| jd| jd| jd| jd
S )Nr8 z (reference=z
, message=z
, context=z , note_stmt=z , hint_stmt=z)>)r> r+ r0 r5 r6 r3 r7 r? r r r __repr__a s 6zDiagnosticPipError.__repr__)r optionsr c c sB | j dkrdnd}d| d| j d| j dV dV |js| jd k rt| j|d| d d| d
d V t| j|d| d d| d
d V qt| j|ddd V n | jV | jd k rdV | jV | jd k s| jd k rdV | jd k rt| j|ddd V | jd k r t| j|ddd V | jd k r>dV d| j V d S )Nr1 redyellow[z bold]z [/]: [bold]z[/] u ]×[/] u ]│[/] )r r u ]╰─>[/] z] [/] u [red]×[/] z z[magenta bold]note[/]: z z[cyan bold]hint[/]: zLink: ) r2 r0
ascii_onlyr6 r( r5 r3 r7 r4 )r? r rD colourr r r __rich_console__l s\
z#DiagnosticPipError.__rich_console__)r+ r, r- r. str__annotations__r r r r= rC r r
r rK
__classcell__r r r@ r r/ 6 s*
r/ c @ s e Zd ZdZdS )ConfigurationErrorz"General exception in configurationNr* r r r r rO s rO c @ s e Zd ZdZdS )InstallationErrorz%General exception during installationNr* r r r r rP s rP c @ s e Zd ZdZdS )UninstallationErrorz'General exception during uninstallationNr* r r r r rQ s rQ c s, e Zd ZdZdZedd fdd Z ZS ) MissingPyProjectBuildRequireszNRaised when pyproject.toml has `build-system`, but no `build-system.requires`.z'missing-pyproject-build-system-requiresN)packager c s* t jdt| tddtdd d S )NCan not process zrThis package has an invalid pyproject.toml file.
The [build-system] table is missing the mandatory `requires` key.;This is an issue with the package mentioned above, not pip.+See PEP 518 for the detailed specification.r5 r6 r3 r7 r< r= r r )r? rS r@ r r r= s z&MissingPyProjectBuildRequires.__init__r+ r, r- r. r0 rL r= rN r r r@ r rR s rR c s. e Zd ZdZdZeedd fdd Z ZS ) InvalidPyProjectBuildRequiresz>Raised when pyproject.toml an invalid `build-system.requires`.z'invalid-pyproject-build-system-requiresN)rS reasonr c s0 t jdt| td| dtdd d S )NrT zKThis package has an invalid `build-system.requires` key in pyproject.toml.
rU rV rW rX )r? rS r[ r@ r r r= s z&InvalidPyProjectBuildRequires.__init__rY r r r@ r rZ s rZ c @ s0 e Zd ZdZdeddddZeddd ZdS )
NoneMetadataErrora4 Raised when accessing a Distribution's "METADATA" or "PKG-INFO".
This signifies an inconsistency, when the Distribution claims to have
the metadata file (if not, raise ``FileNotFoundError`` instead), but is
not actually able to produce its content. This may be due to permission
errors.
r N)dist
metadata_namer c C s || _ || _dS )z
:param dist: A Distribution object.
:param metadata_name: The name of the metadata being accessed
(can be "METADATA" or "PKG-INFO").
N)r] r^ )r? r] r^ r r r r= s
zNoneMetadataError.__init__rA c C s d | j| jS )Nz+None {} metadata found for distribution: {})formatr^ r] rB r r r __str__ s zNoneMetadataError.__str__r+ r, r- r. rL r= r` r r r r r\ s
r\ c @ s e Zd ZdZedddZdS )UserInstallationInvalidzBA --user install is requested on an environment without user site.rA c C s dS )Nz$User base directory is not specifiedr rB r r r r` s z UserInstallationInvalid.__str__N)r+ r, r- r. rL r` r r r r rb s rb c @ s e Zd ZedddZdS )InvalidSchemeCombinationrA c C s6 d dd | jd d D }d| d| jd dS )Nz, c s s | ]}t |V qd S N)rL ).0ar r r s z3InvalidSchemeCombination.__str__..z Cannot set z and z together)r% args)r? beforer r r r` s z InvalidSchemeCombination.__str__N)r+ r, r- rL r` r r r r rc s rc c @ s e Zd ZdZdS )DistributionNotFoundzCRaised when a distribution cannot be found to satisfy a requirementNr* r r r r rk s rk c @ s e Zd ZdZdS )RequirementsFileParseErrorzDRaised when a general error occurs parsing a requirements file line.Nr* r r r r rl
s rl c @ s e Zd ZdZdS )BestVersionAlreadyInstalledzNRaised when the most up-to-date version of a package is already
installed.Nr* r r r r rm s rm c @ s e Zd ZdZdS )
BadCommandz0Raised when virtualenv or a command is not foundNr* r r r r rn s rn c @ s e Zd ZdZdS ) CommandErrorz7Raised when there is an error in command-line argumentsNr* r r r r ro s ro c @ s e Zd ZdZdS )PreviousBuildDirErrorz:Raised when there's a previous conflicting build directoryNr* r r r r rp s rp c s< e Zd ZdZd eeedd fdd
ZedddZ Z S )
NetworkConnectionErrorzHTTP connection errorN) error_msgresponserequestr c sJ || _ || _|| _| j dk r6| js6t|dr6| j j| _t ||| dS )zc
Initialize NetworkConnectionError with `request` and `response`
objects.
Nrt )rs rt rr r: r< r= )r? rr rs rt r@ r r r= " s
z NetworkConnectionError.__init__rA c C s
t | jS rd )rL rr rB r r r r` 4 s z NetworkConnectionError.__str__)NN)
r+ r, r- r. rL r r
r= r` rN r r r@ r rq s rq c @ s e Zd ZdZdS )InvalidWheelFilenamezInvalid wheel filename.Nr* r r r r ru 8 s ru c @ s e Zd ZdZdS )UnsupportedWheelzUnsupported wheel.Nr* r r r r rv < s rv c @ s. e Zd ZdZeedddZedddZdS ) InvalidWheelz Invalid (e.g. corrupt) wheel.locationnamec C s || _ || _d S rd rx )r? ry rz r r r r= C s zInvalidWheel.__init__rA c C s d| j d| j dS )NzWheel 'z
' located at z is invalid.)rz ry rB r r r r` G s zInvalidWheel.__str__Nra r r r r rw @ s rw c @ s4 e Zd ZdZdeeeddddZeddd ZdS )
MetadataInconsistentzBuilt metadata contains inconsistent information.
This is raised when the metadata contains values (e.g. name and version)
that do not match the information previously obtained from sdist filename
or user-supplied ``#egg=`` value.
r N)ireqfieldf_valm_valr c C s || _ || _|| _|| _d S rd )r| r} r~ r )r? r| r} r~ r r r r r= S s z MetadataInconsistent.__init__rA c C s d}| | j| j| j| jS )NzJRequested {} has inconsistent {}: filename has {!r}, but metadata has {!r})r_ r| r} r~ r )r? templater r r r` [ s z MetadataInconsistent.__str__ra r r r r r{ K s r{ c s, e Zd ZdZdZedd fdd Z ZS )LegacyInstallFailurez1Error occurred while executing `setup.py install`zlegacy-install-failureNpackage_detailsr c s t jd|ddd d S )Nz2Encountered error while trying to install package.z&See above for output from the failure.rU r5 r6 r7 r3 )r< r= r? r r@ r r r= h s z LegacyInstallFailure.__init__rY r r r@ r r c s r c sF e Zd ZdZdZeeeee dd fdd Z eddd Z
Z S )
InstallationSubprocessErrorzA subprocess call failed.z subprocess-exited-with-errorN)command_description exit_code output_linesr c st |d krt d}n.t dt| dt d| t d }t jdt| d| |d dd || _|| _d S )
NzSee above for output.z[red][z lines of output][/]
rH z[red]\[end of output][/]z[green]z)[/] did not run successfully.
exit code: zNThis error originates from a subprocess, and is likely not a problem with pip.r ) r from_markuplenr% r< r= r r r )r? r r r
output_promptr@ r r r= v s
z$InstallationSubprocessError.__init__rA c C s | j d| j S )Nz
exited with )r r rB r r r r` s z#InstallationSubprocessError.__str__) r+ r, r- r. r0 rL intr r r= r` rN r r r@ r r q s
r c s6 e Zd ZdZedd fdd ZedddZ ZS ) MetadataGenerationFailedzmetadata-generation-failedNr c s t t| jdt|ddd d S )Nz4Encountered error while generating package metadata.zSee above for details.rU r )r< r r= r r r@ r r r= s
z!MetadataGenerationFailed.__init__rA c C s dS )Nzmetadata generation failedr rB r r r r` s z MetadataGenerationFailed.__str__)r+ r, r- r0 rL r= r` rN r r r@ r r s
r c @ sJ e Zd ZdZddddZddddd Zedd
d Zedd d
Z dS )
HashErrorsz:Multiple HashError instances rolled into one for reportingNrA c C s
g | _ d S rd )errorsrB r r r r= s zHashErrors.__init__ HashError)r1 r c C s | j | d S rd )r append)r? r1 r r r r s zHashErrors.appendc C sb g }| j jdd d t| j dd D ](\}}||j |dd |D q&|r^d|S dS ) Nc S s | j S rd )orderer r r z$HashErrors.__str__..)keyc S s | j S rd r@ r r r r r r c s s | ]}| V qd S rd )bodyre r r r r rg s z%HashErrors.__str__..r! rH )r sortr r headextendr% )r? linescls
errors_of_clsr r r r` s
zHashErrors.__str__c C s
t | jS rd )boolr rB r r r __bool__ s zHashErrors.__bool__)
r+ r, r- r. r= r rL r` r r r r r r r s
r c @ s\ e Zd ZU dZdZed ed< dZdZe ed< e
dd d
Z e
dd d Z e
dd
dZ
dS )r a
A failure to verify a package against known-good hashes
:cvar order: An int sorting hash exception classes by difficulty of
recovery (lower being harder), so the user doesn't bother fretting
about unpinned packages when he has deeper issues, like VCS
dependencies, to deal with. Also keeps error reports in a
deterministic order.
:cvar head: A section heading for display above potentially many
exceptions of this kind
:ivar req: The InstallRequirement that triggered this error. This is
pasted on after the exception is instantiated, because it's not
typically available earlier.
Nr reqrH rh r rA c C s d| S )a= Return a summary of me for display under the heading.
This default implementation simply prints a description of the
triggering requirement.
:param req: The InstallRequirement that provoked this error, with
its link already populated by the resolver's _populate_link().
z )_requirement_namerB r r r r s
zHashError.bodyc C s | j d| S )Nr! )r r rB r r r r` s zHashError.__str__c C s | j rt| j S dS )zReturn a description of the requirement that triggered me.
This default implementation returns long description of the req, with
line numbers
unknown package)r rL rB r r r r s zHashError._requirement_name)r+ r, r- r. r r rM r r r rL r r` r r r r r r s
r c @ s e Zd ZdZdZdZdS )VcsHashUnsupporteduA hash was provided for a version-control-system-based requirement, but
we don't have a method for hashing those.r zlCan't verify hashes for these requirements because we don't have a way to hash version control repositories:Nr+ r, r- r. r r r r r r r s r c @ s e Zd ZdZdZdZdS )DirectoryUrlHashUnsupportedr zUCan't verify hashes for these file:// requirements because they point to directories:Nr r r r r r s r c @ s6 e Zd ZdZdZdZeddddZedd d
ZdS ) HashMissingz2A hash was needed for a requirement but is absent. aw Hashes are required in --require-hashes mode, but they are missing from some requirements. Here is a list of those requirements along with the hashes their downloaded archives actually had. Add lines like these to your requirements files to prevent tampering. (If you did not enable --require-hashes manually, note that it turns on automatically when any package has a hash.)N) gotten_hashr c C s
|| _ dS )zq
:param gotten_hash: The hash of the (possibly malicious) archive we
just downloaded
N)r )r? r r r r r= s zHashMissing.__init__rA c C sH ddl m} d }| jr4| jjr&| jjn t| jdd }d|p>d|| jS )Nr )
FAVORITE_HASHr z {} --hash={}:{}r )pip._internal.utils.hashesr r
original_linkgetattrr_ r )r? r rS r r r r s
zHashMissing.body) r+ r, r- r. r r rL r= r r r r r r s
r c @ s e Zd ZdZdZdZdS ) HashUnpinnedzPA requirement had a hash specified but was not pinned to a specific
version. zaIn --require-hashes mode, all requirements must have their versions pinned with ==. These do not:Nr r r r r r 2 s r c @ sZ e Zd ZdZdZdZeeee f eedf ddddZ ed d
d Z
ed d d
Z dS ) HashMismatchz
Distribution file hash values don't match.
:ivar package_name: The name of the package that triggered the hash
mismatch. Feel free to write to this after the exception is raise to
improve its error message.
zTHESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.r N)allowedgotsr c C s || _ || _dS )z
:param allowed: A dict of algorithm names pointing to lists of allowed
hex digests
:param gots: A dict of algorithm names pointing to hashes we
actually got from the files under suspicion
N)r r )r? r r r r r r= O s zHashMismatch.__init__rA c C s d | | S )Nz
{}:
{})r_ r _hash_comparisonrB r r r r Y s zHashMismatch.bodyc sl t dddd}g }| j D ]B\}}|| | fdd|D |d| j| q d|S ) aE
Return a comparison of actual and expected hash values.
Example::
Expected sha256 abcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcde
or 123451234512345123451234512345123451234512345
Got bcdefbcdefbcdefbcdefbcdefbcdefbcdefbcdefbcdef
z
chain[str]) hash_namer c S s t | gtdS )Nz or)r r )r r r r hash_then_orh s z3HashMismatch._hash_comparison..hash_then_orc 3 s | ]}d t |V qdS )z Expected {} {}N)r_ nextr r r r rg p s z0HashMismatch._hash_comparison..z Got {}
r! ) rL r itemsr r r_ r hexdigestr% )r? r r r expectedsr r r r \ s z HashMismatch._hash_comparison) r+ r, r- r. r r r rL r r= r r r r r r r = s &
r c @ s e Zd ZdZdS )UnsupportedPythonVersionzMUnsupported python version according to Requires-Python package
metadata.Nr* r r r r r y s r c sF e Zd ZdZd
eee eej dd fdd
Zeddd Z Z
S ) !ConfigurationFileCouldNotBeLoadedz8When there are errors while loading a configuration filecould not be loadedN)r[ fnamer1 r c s" t | || _|| _|| _d S rd )r< r= r[ r r1 )r? r[ r r1 r@ r r r= s z*ConfigurationFileCouldNotBeLoaded.__init__rA c C sF | j d k rd| j d}n | jd k s(td| j d}d| j | S )Nz in .z.
r! zConfiguration file )r r1 r; r[ )r? message_partr r r r` s
z)ConfigurationFileCouldNotBeLoaded.__str__)r NN) r+ r, r- r. rL r configparserErrorr= r` rN r r r@ r r ~ s r )Er. r r itertoolsr r r typingr r r r r Zpip._vendor.requests.modelsr
r pip._vendor.rich.consoler r
r Zpip._vendor.rich.markupr pip._vendor.rich.textr hashlibr r pip._internal.metadatar Z pip._internal.req.req_installr rL r r r( Exceptionr) r/ rO rP rQ rR rZ r\ rb rc rk rl rm rn ro rp rq ru rv rw r{ r r r r r r r r r r r r r r r r sj
v ). * <