File: //usr/local/lib/python3.10/site-packages/pip/_internal/__pycache__/exceptions.cpython-310.pyc
o
��i�^ �
@ sX d Z ddlZddlZddlZddlZddlZddlZddlZddlm Z m
Z
m Z ddl m
Z
mZmZmZmZmZ ddlmZmZ ddlmZmZmZ ddlmZ ddl m Z e
rpdd l m Z dd
l m Z dd l!m"Z" dd l#m$Z$ e�%e&�Z'd
e(de)fdd�Z*d
ee e(f dede(de(de f
dd�Z+G dd� de,�Z-G dd� de-�Z.G dd� de-�Z/G d d � d e-�Z0G d d � d e-�Z1G d d!� d!e.�Z2G d"d#� d#e.�Z3G d$d%� d%e-�Z4G d&d'� d'e0�Z5G d(d)� d)e0�Z6G d*d+� d+e0�Z7G d,d-� d-e0�Z8G d.d/� d/e-�Z9G d0d1� d1e-�Z:G d2d3� d3e-�Z;G d4d5� d5e-�Z<G d6d7� d7e-�Z=G d8d9� d9e0�Z>G d:d;� d;e0�Z?G d<d=� d=e0�Z@G d>d?� d?e0�ZAG d@dA� dAe.�ZBG dBdC� dCe.e0�ZCG dDdE� dEeCe0�ZDG dFdG� dGe0�ZEG dHdI� dIe0�ZFG dJdK� dKeF�ZGG dLdM� dMeF�ZHG dNdO� dOeF�ZIG dPdQ� dQeF�ZJG dRdS� dSeF�ZKG dTdU� dUe0�ZLG dVdW� dWe/�ZMdXejN� dY�ZOG dZd[� d[e.�ZPdS )\z�Exceptions 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)�chain�groupby�repeat)�
TYPE_CHECKING�Dict�Iterator�List�Optional�Union)�Request�Response)�Console�ConsoleOptions� RenderResult)�escape)�Text)�_Hash)�Literal)�BaseDistribution)�InstallRequirement�s�returnc C s t �d| �d uS )Nz^[a-z]+(-[a-z]+)*$)�re�match)r � r �C/usr/local/lib/python3.10/site-packages/pip/_internal/exceptions.py�_is_kebab_case$ � r �console�prefix�indentc C sJ t | t�r| }n|�| �}|j|dd�|jd|� �dd��|jdd�� S )N�ignore)�overflow�
T)� allow_blank)�
isinstancer �
render_str�join�split)r r r r �textr r r �_prefix_with_indent( s
��r* c @ � e Zd ZdZdS )�PipErrorzThe base pip error.N��__name__�
__module__� __qualname__�__doc__r r r r r, 9 � r, c s� e Zd ZU dZeed< ddddd�dddee deeef d eeeef d
eeeef d eeeef d ee d
df� fdd�Z d
efdd�Z
de de d
e
fdd�Z� 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`.
� reference�errorN)�kindr4 � note_stmt�linkr6 zLiteral["error", "warning"]�message�context� hint_stmtr7 r8 r c s~ |d u rt | d�s
J d��| j}t|�sJ d��|| _|| _|| _|| _|| _|| _|| _t � �
d| j j � d| j� d�� d S )Nr4 z error reference not provided!z#error reference must be kebab-case!�<z: �>)
�hasattrr4 r r6 r9 r: r7 r; r8 �super�__init__� __class__r. )�selfr6 r4 r9 r: r; r7 r8 �rA r r r@ J s $zDiagnosticPipError.__init__c
C s8 d| j j� d| j�d| j�d| j�d| j�d| j�d�
S )Nr< z (reference=z
, message=z
, context=z , note_stmt=z , hint_stmt=z)>)rA r. r4 r9 r: r7 r; �rB r r r �__repr__h s ������zDiagnosticPipError.__repr__r �optionsc c sD � | j dkrdnd}d|� d| j � d| j� d�V dV |jsT| jd urIt| j|d|� d �d|� d
�d �V t| j|d|� d �d|� d
�d �V nt| j|ddd �V n| jV | jd urddV | jV | jd usn| jd urqdV | jd ur�t| j|ddd �V | jd ur�t| j|ddd �V | jd ur�dV d| j� �V d S d S )Nr5 �red�yellow�[z bold]z [/]: [bold]z[/]� u ]×[/] u ]│[/] )r r u ]╰─>[/] z] [/] u [red]×[/] z z[magenta bold]note[/]: z z[cyan bold]hint[/]: zLink: ) r6 r4 �
ascii_onlyr: r* r9 r7 r; r8 )rB r rF �colourr r r �__rich_console__s s` �
�
�
�
�
�
�z#DiagnosticPipError.__rich_console__)r. r/ r0 r1 �str�__annotations__r r
r r@ rE r
r r rM �
__classcell__r r rC r r3 = s@
���
���� �
� ���r3 c @ r+ )�ConfigurationErrorz"General exception in configurationNr- r r r r rQ � r2 rQ c @ r+ )�InstallationErrorz%General exception during installationNr- r r r r rR � r2 rR c @ r+ )�UninstallationErrorz'General exception during uninstallationNr- r r r r rS � r2 rS c �. e Zd ZdZdZdeddf� fdd� Z� ZS )� MissingPyProjectBuildRequireszNRaised when pyproject.toml has `build-system`, but no `build-system.requires`.z'missing-pyproject-build-system-requires�packager Nc s* t � jdt|�� �td�dtd�d� d S )N�Can 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.�r9 r: r7 r; �r? r@ r r )rB rV rC r r r@ � s �
�z&MissingPyProjectBuildRequires.__init__�r. r/ r0 r1 r4 rN r@ rP r r rC r rU � � rU c s2 e Zd ZdZdZdededdf� fdd� Z� ZS ) � InvalidPyProjectBuildRequiresz>Raised when pyproject.toml an invalid `build-system.requires`.z'invalid-pyproject-build-system-requiresrV �reasonr Nc s0 t � jdt|�� �td|� ��dtd�d� d S )NrW zKThis package has an invalid `build-system.requires` key in pyproject.toml.
rX rY rZ r[ )rB rV r_ rC r r r@ � s ��
�z&InvalidPyProjectBuildRequires.__init__r\ r r rC r r^ � s "r^ c @ s4 e Zd ZdZdddeddfdd�Zdefd d
�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.
�distr �
metadata_namer Nc C � || _ || _dS )z�
:param dist: A Distribution object.
:param metadata_name: The name of the metadata being accessed
(can be "METADATA" or "PKG-INFO").
N)ra rb )rB ra rb r r r r@ � s
zNoneMetadataError.__init__c C s d� | j| j�S )Nz+None {} metadata found for distribution: {})�formatrb ra rD r r r �__str__� s �zNoneMetadataError.__str__�r. r/ r0 r1 rN r@ re r r r r r` � s ��
�
r` c @ s e Zd ZdZdefdd�ZdS )�UserInstallationInvalidzBA --user install is requested on an environment without user site.r c C � dS )Nz$User base directory is not specifiedr rD r r r re � z UserInstallationInvalid.__str__N)r. r/ r0 r1 rN re r r r r rg s rg c @ s e Zd Zdefdd�ZdS )�InvalidSchemeCombinationr c C s6 d� dd� | jd d� D ��}d|� d| jd � d�S )Nz, c s s � | ]}t |�V qd S �N)rN )�.0�ar r r � <genexpr> � � z3InvalidSchemeCombination.__str__.<locals>.<genexpr>���z Cannot set z and z together)r' �args)rB �beforer r r re s z InvalidSchemeCombination.__str__N)r. r/ r0 rN re r r r r rj s rj c @ r+ )�DistributionNotFoundzCRaised when a distribution cannot be found to satisfy a requirementNr- r r r r rs
r2 rs c @ r+ )�RequirementsFileParseErrorzDRaised when a general error occurs parsing a requirements file line.Nr- r r r r rt r2 rt c @ r+ )�BestVersionAlreadyInstalledzNRaised when the most up-to-date version of a package is already
installed.Nr- r r r r ru r2 ru c @ r+ )�
BadCommandz0Raised when virtualenv or a command is not foundNr- r r r r rv r2 rv c @ r+ )� CommandErrorz7Raised when there is an error in command-line argumentsNr- r r r r rw r2 rw c @ r+ )�PreviousBuildDirErrorz:Raised when there's a previous conflicting build directoryNr- r r r r rx " r2 rx c sN e Zd ZdZ d dedee dee ddf� fdd�
Zdefd d
�Z � Z
S ) �NetworkConnectionErrorzHTTP connection errorN� error_msg�response�requestr c sJ || _ || _|| _| j dur| jst|d�r| j j| _t� �|||� dS )zc
Initialize NetworkConnectionError with `request` and `response`
objects.
Nr| )r{ r| rz r> r? r@ )rB rz r{ r| rC r r r@ ) s
��
z NetworkConnectionError.__init__c C �
t | j�S rk )rN rz rD r r r re > �
z NetworkConnectionError.__str__)NN) r. r/ r0 r1 rN r r r r@ re rP r r rC r ry & s �����ry c @ r+ )�InvalidWheelFilenamezInvalid wheel filename.Nr- r r r r r B r2 r c @ r+ )�UnsupportedWheelzUnsupported wheel.Nr- r r r r r� F r2 r� c @ s0 e Zd ZdZdedefdd�Zdefdd�Zd S )
� InvalidWheelz Invalid (e.g. corrupt) wheel.�location�namec C s || _ || _d S rk )r� r� )rB r� r� r r r r@ M s
zInvalidWheel.__init__r c C s d| j � d| j� d�S )NzWheel 'z
' located at z is invalid.)r� r� rD r r r re Q s zInvalidWheel.__str__Nrf r r r r r� J s r� c
@ s< e Zd ZdZdddedededdf
d d
�Zdefd d �ZdS )
�MetadataInconsistenta Built 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,
user-supplied ``#egg=`` value, or an install requirement name.
�ireqr �field�f_val�m_valr Nc C s || _ || _|| _|| _d S rk �r� r� r� r� )rB r� r� r� r� r r r r@ ] s
z MetadataInconsistent.__init__c C s$ d| j � d| j� d| j�d| j��S )Nz
Requested z has inconsistent z : expected z, but metadata has r� rD r r r re e s ���z MetadataInconsistent.__str__rf r r r r r� U s ����
�r� c rT )�LegacyInstallFailurez1Error occurred while executing `setup.py install`zlegacy-install-failure�package_detailsr Nc s t � jd|ddd� d S )Nz2Encountered error while trying to install package.z&See above for output from the failure.rX �r9 r: r; r7 )r? r@ �rB r� rC r r r@ q s
�z LegacyInstallFailure.__init__r\ r r rC r r� l r] r� c sL e Zd ZdZdZdededeee ddf� fdd � Z defd
d �Z
� Z S ) �InstallationSubprocessErrorzA subprocess call failed.z subprocess-exited-with-error�command_description� exit_code� output_linesr Nc st |d u r t d�}nt �dt|�� d��t d�|�� t �d� }t� jdt|�� d|� �|d dd � || _|| _d S )
NzSee above for output.z[red][z lines of output][/]
rJ 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_markup�lenr' r? r@ r r� r� )rB r� r� r� �
output_promptrC r r r@ s$
��� ��
z$InstallationSubprocessError.__init__c C s | j � d| j� �S )Nz
exited with )r� r� rD r r r re � s z#InstallationSubprocessError.__str__) r. r/ r0 r1 r4 rN �intr r r@ re rP r r rC r r� z s ��
�� r� c s8 e Zd ZdZdeddf� fdd� Zdefdd�Z� ZS ) �MetadataGenerationFailedzmetadata-generation-failedr� r Nc s t t| �jdt|�ddd� d S )Nz4Encountered error while generating package metadata.zSee above for details.rX r� )r? r� r@ r r� rC r r r@ � s
�z!MetadataGenerationFailed.__init__c C rh )Nzmetadata generation failedr rD r r r re � ri z MetadataGenerationFailed.__str__)r. r/ r0 r4 rN r@ re rP r r rC r r� � s �� r� c @ s@ e Zd ZdZddd�Zddd �Zdefd
d �Zdefd d
�Z dS )�
HashErrorsz:Multiple HashError instances rolled into one for reportingr Nc C s
g | _ d S rk )�errorsrD r r r r@ � r~ zHashErrors.__init__r5 � HashErrorc C s | j �|� d S rk )r� �append)rB r5 r r r r� � r zHashErrors.appendc C sb g }| j jdd� d� t| j dd� �D ]\}}|�|j� |�dd� |D �� q|r/d�|�S dS ) Nc S � | j S rk )�order��er r r �<lambda>� � z$HashErrors.__str__.<locals>.<lambda>)�keyc S r� rk rC r� r r r r� � r� c s s � | ]}|� � V qd S rk )�body�rl r� r r r rn � ro z%HashErrors.__str__.<locals>.<genexpr>r# rJ )r� �sortr r� �head�extendr' )rB �lines�cls�
errors_of_clsr r r re � s
zHashErrors.__str__c C r} rk )�boolr� rD r r r �__bool__� r~ zHashErrors.__bool__)r N)r5 r� r N)
r. r/ r0 r1 r@ r� rN re r� r� r r r r r� � s
r� c @ s\ e Zd ZU dZdZed ed< dZdZe ed< de
fd d
�Z de
fd d �Z de
fd
d�Z
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 �reqrJ rp r� r 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_namerD r r r r� � s
zHashError.bodyc C s | j � d| �� � �S )Nr# )r� r� rD r r r re � � zHashError.__str__c C s | j rt| j �S dS )z�Return a description of the requirement that triggered me.
This default implementation returns long description of the req, with
line numbers
�unknown package)r� rN rD r r r r� � s zHashError._requirement_name)r. r/ r0 r1 r� r rO r� r� r� rN r� re r� r r r r r� � s
r� c @ � e Zd ZdZdZdZdS )�VcsHashUnsupported�uA 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:N�r. r/ r0 r1 r� r� r r r r r� � �
�r� c @ r� )�DirectoryUrlHashUnsupportedr� � zUCan't verify hashes for these file:// requirements because they point to directories:Nr� r r r r r� r� r� c @ s8 e Zd ZdZdZdZdeddfdd�Zdefd 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.)� gotten_hashr Nc C s
|| _ dS )zq
:param gotten_hash: The hash of the (possibly malicious) archive we
just downloaded
N)r� )rB r� r r r r@ s
zHashMissing.__init__c C sH ddl m} d }| jr| jjr| jjnt| jdd �}d�|p d|| j�S )Nr )�
FAVORITE_HASHr� z {} --hash={}:{}r� )�pip._internal.utils.hashesr� r� �
original_link�getattrrd r� )rB r� rV r r r r� & s
� � �zHashMissing.body) r. r/ r0 r1 r� r� rN r@ r� r r r r r� s �
r� c @ r� )� 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� ; r� r� c @ s^ e Zd ZdZdZdZdeeee f deedf ddfd d
�Z defd d �Z
defd
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.
� z�THESE 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.�allowed�gotsr r Nc C rc )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� )rB r� r� r r r r@ X s
zHashMismatch.__init__c C s d� | �� | �� �S )Nz
{}:
{})rd r� �_hash_comparisonrD r r r r� b r� zHashMismatch.bodyc sn dt ddfdd�}g }| j�� D ]!\}}||�� |�� fdd�|D �� |�d�| j| �� �� qd �|�S )
aE
Return a comparison of actual and expected hash values.
Example::
Expected sha256 abcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcde
or 123451234512345123451234512345123451234512345
Got bcdefbcdefbcdefbcdefbcdefbcdefbcdefbcdefbcdef
� hash_namer z
chain[str]c S s t | gtd��S )Nz or)r r )r� r r r � hash_then_orq s z3HashMismatch._hash_comparison.<locals>.hash_then_orc 3 s � | ] }d � t� �|�V qdS )z Expected {} {}N)rd �nextr� �r r r rn y s �
�z0HashMismatch._hash_comparison.<locals>.<genexpr>z Got {}
r# ) rN r� �itemsr� r� rd r� � hexdigestr' )rB r� r� r� � expectedsr r� r r� e s ��
z HashMismatch._hash_comparison) r. r/ r0 r1 r� r� r rN r r@ r� r� r r r r r� F s �*
r� c @ r+ )�UnsupportedPythonVersionzMUnsupported python version according to Requires-Python package
metadata.Nr- r r r r r� � r2 r� c sR e Zd ZdZ d dedee deej ddf� fdd �
Zdefd
d �Z � Z
S )
�!ConfigurationFileCouldNotBeLoadedz8When there are errors while loading a configuration file�could not be loadedNr_ �fnamer5 r c s" t � �|� || _|| _|| _d S rk )r? r@ r_ r� r5 )rB r_ r� r5 rC r r r@ � s
z*ConfigurationFileCouldNotBeLoaded.__init__c C sF | j d ur
d| j � d�}n| jd usJ �d| j� d�}d| j� |� �S )Nz in �.z.
r# zConfiguration file )r� r5 r_ )rB � message_partr r r re � s
z)ConfigurationFileCouldNotBeLoaded.__str__)r� NN) r. r/ r0 r1 rN r � configparser�Errorr@ re rP r r rC r r� � s ����� r� z The Python environment under z� is managed externally, and may not be
manipulated by the user. Please use specific tooling from the distributor of
the Python installation to interact with this environment instead.
c sh e Zd ZdZdZdee ddf� fdd� Zede e fdd ��Z
e d
e e
jef dd fd d ��Z� ZS )
� ExternallyManagedEnvironmentaP The current environment is externally managed.
This is raised when the current environment is externally managed, as
defined by `PEP 668`_. The ``EXTERNALLY-MANAGED`` configuration is checked
and displayed when the error is bubbled up to the user.
:param error: The error message read from ``EXTERNALLY-MANAGED``.
z externally-managed-environmentr5 r Nc s6 |d u r t t�}nt |�}t� jd|dt d�d� d S )Nz&This environment is externally managedz�If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.z+See PEP 668 for the detailed specification.rZ )r �!_DEFAULT_EXTERNALLY_MANAGED_ERRORr? r@ )rB r5 r: rC r r r@ � s
�z%ExternallyManagedEnvironment.__init__c c s| � zt j} W n ty d }Y nw t �| �\}}|d ur9d|� �V dD ]}|�|�\}}}|s2q%d|� �V q%dV d S )NzError-)�-�_r� )�locale� LC_MESSAGES�AttributeError� getlocale� partition)�category�langr� �seprr �foundr r r �#_iter_externally_managed_error_keys� s �
�
z@ExternallyManagedEnvironment._iter_externally_managed_error_keys�configc
C s� t jd d�}z5|j|dd� |d }| �� D ] }t�t�� | || �W d � W S 1 s1w Y qW | d �S tyG Y | d �S ttt j fyi ddl
m } t �
|�}t jd||d� Y | d �S w ) N)�
interpolationzutf-8)�encodingzexternally-managedr )�VERBOSEzFailed to read %s)�exc_info)r� � ConfigParser�readr� �
contextlib�suppress�KeyError�OSError�UnicodeDecodeError� ParsingError�pip._internal.utils._logr� �logger� isEnabledFor�warning)r� r� �parser�sectionr� r� r� r r r � from_config� s&
(��
��
�z(ExternallyManagedEnvironment.from_config)r. r/ r0 r1 r4 r rN r@ � staticmethodr r� � classmethodr
�pathlib�Pathr� rP r r rC r r� � s ��r� )Qr1 r� r� r� �loggingr� r �sys� itertoolsr r r �typingr r 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 � getLoggerr. r� rN r� r r* � Exceptionr, r3 rQ rR rS rU r^ r` rg rj rs rt ru rv rw rx ry r r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r r� r� r r r r �<module> s�
����
�v ). * <�