관리-도구
편집 파일: exceptions.cpython-38.pyc
U &?�fc � @ sV d Z ddlZddlZddlZddlZddlZddlZddlZddlm Z m Z m Z ddl m Z mZmZmZmZmZmZ ddlmZmZmZ ddlmZ ddlmZ e r�ddl m Z dd l m Z m Z dd l!m"Z" dd l#m$Z$ e�%e&�Z'e(e)d �d d�Z*eee(f ee(e(ed�dd�Z+G dd� de,�Z-G dd� de-�Z.G dd� de-�Z/G dd� de-�Z0G dd� de.�Z1G d d � d e.�Z2G d d � d e-�Z3G d d!� d!e0�Z4G d"d#� d#e0�Z5G d$d%� d%e0�Z6G d&d'� d'e0�Z7G d(d)� d)e-�Z8G d*d+� d+e-�Z9G d,d-� d-e-�Z:G d.d/� d/e-�Z;G d0d1� d1e-�Z<G d2d3� d3e0�Z=G d4d5� d5e0�Z>G d6d7� d7e0�Z?G d8d9� d9e0�Z@G d:d;� d;e0�ZAG d<d=� d=e.e0�ZBG d>d?� d?eBe0�ZCG d@dA� dAe0�ZDG dBdC� dCe0�ZEG dDdE� dEeE�ZFG dFdG� dGeE�ZGG dHdI� dIeE�ZHG dJdK� dKeE�ZIG dLdM� dMeE�ZJG dNdO� dOe0�ZKG dPdQ� dQe/�ZLdRejM� dS�ZNG dTdU� dUe.�ZOG dVdW� dWe.�ZPG dXdY� dYe.�ZQdS )Zz�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�Literal�Optional�Union)�Console�ConsoleOptions� RenderResult)�escape)�Text)�_Hash)�Request�Response)�BaseDistribution)�InstallRequirement)�s�returnc C s t �d| �d k S )Nz^[a-z]+(-[a-z]+)*$)�re�match)r � r �F/opt/hc_python/lib/python3.8/site-packages/pip/_internal/exceptions.py�_is_kebab_case$ s r )r �console�prefix�indentr c 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 @ s e Zd ZdZdS )�PipErrorzThe base pip error.N��__name__� __module__� __qualname__�__doc__r r r r r* 9 s r* c s� e Zd ZU dZeed< ddddd�dee eeef eeeef eeeef eeeef ee dd�� fdd �Z ed �d d �Z e e e d �dd�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)�kindr1 � note_stmt�linkzLiteral["error", "warning"])r3 r1 �message�context� hint_stmtr4 r5 r c s~ |d kr t | d�std��| j}t|�s0td��|| _|| _|| _|| _|| _|| _|| _ t � � d| j j � d| j� d�� d S )Nr1 z error reference not provided!z#error reference must be kebab-case!�<z: �>)�hasattr�AssertionErrorr1 r r3 r6 r7 r4 r8 r5 �super�__init__� __class__r, )�selfr3 r1 r6 r7 r8 r4 r5 �r? r r r> J s zDiagnosticPipError.__init__�r c C s8 d| j j� d| j�d| j�d| j�d| j�d| j�d� S )Nr9 z (reference=z , message=z , context=z , note_stmt=z , hint_stmt=z)>)r? r, r1 r6 r7 r4 r8 �r@ r r r �__repr__h s 6�zDiagnosticPipError.__repr__)r �optionsr c c sB | j dkrdnd}d|� d| j � d| j� d�V dV |js�| jd k r�t| j|d|� d �d|� d �d �V t| j|d|� d �d|� d �d �V q�t| j|ddd �V n | jV | jd k r�dV | jV | jd k s�| jd k r�dV | jd k r�t| j|ddd �V | jd k �r t| j|ddd �V | jd k �r>dV d| j� �V d S )Nr2 �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: ) r3 r1 � ascii_onlyr7 r) r6 r4 r8 r5 )r@ r rE �colourr r r �__rich_console__s s\ � � � � � z#DiagnosticPipError.__rich_console__)r, r- r. r/ �str�__annotations__r r r r> rD r r r rL � __classcell__r r rA r r0 = s* � � �r0 c @ s e Zd ZdZdS )�ConfigurationErrorz"General exception in configurationNr+ r r r r rP � s rP c @ s e Zd ZdZdS )�InstallationErrorz%General exception during installationNr+ 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|�� �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.�r6 r7 r4 r8 �r= r> r r )r@ rS rA r r r> � s ��z&MissingPyProjectBuildRequires.__init__�r, r- r. r/ r1 rM r> rO r r rA 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|� ��dtd�d� d S )NrT zKThis package has an invalid `build-system.requires` key in pyproject.toml. rU rV rW rX )r@ rS r[ rA r r r> � s ��z&InvalidPyProjectBuildRequires.__init__rY r r rA r rZ � s rZ c @ s0 e Zd ZdZdedd�dd�Zed�dd �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__rB c C s d| j � d| j� �S )NzNone z" metadata found for distribution: )r^ r] rC r r r �__str__� s zNoneMetadataError.__str__�r, r- r. r/ rM r> r_ r r r r r\ � s � r\ c @ s e Zd ZdZed�dd�ZdS )�UserInstallationInvalidzBA --user install is requested on an environment without user site.rB c C s dS )Nz$User base directory is not specifiedr rC r r r r_ � s z UserInstallationInvalid.__str__N)r, r- r. r/ rM r_ r r r r ra � s ra c @ s e Zd Zed�dd�ZdS )�InvalidSchemeCombinationrB c C s6 d� dd� | jd d� D ��}d|� d| jd � d�S )Nz, c s s | ]}t |�V qd S �N)rM )�.0�ar r r � <genexpr> s z3InvalidSchemeCombination.__str__.<locals>.<genexpr>���z Cannot set z and z together)r& �args)r@ �beforer r r r_ s z InvalidSchemeCombination.__str__N)r, r- r. rM r_ r r r r rb s rb c @ s e Zd ZdZdS )�DistributionNotFoundzCRaised when a distribution cannot be found to satisfy a requirementNr+ r r r r rj s rj c @ s e Zd ZdZdS )�RequirementsFileParseErrorzDRaised when a general error occurs parsing a requirements file line.Nr+ r r r r rk s rk c @ s e Zd ZdZdS )�BestVersionAlreadyInstalledzNRaised when the most up-to-date version of a package is already installed.Nr+ r r r r rl s rl c @ s e Zd ZdZdS )� BadCommandz0Raised when virtualenv or a command is not foundNr+ r r r r rm s rm c @ s e Zd ZdZdS )� CommandErrorz7Raised when there is an error in command-line argumentsNr+ r r r r rn s rn c @ s e Zd ZdZdS )�PreviousBuildDirErrorz:Raised when there's a previous conflicting build directoryNr+ r r r r ro s ro c sD e Zd ZdZd eed ed dd�� fdd� Zed�d d �Z� ZS ) �NetworkConnectionErrorzHTTP connection errorNr r )� error_msg�response�requestr c sJ || _ || _|| _| j dk r6| js6t|d�r6| j j| _t� �|||� dS )zc Initialize NetworkConnectionError with `request` and `response` objects. Nrs )rr rs rq r; r= r> )r@ rq rr rs rA r r r> " s ��� z NetworkConnectionError.__init__rB c C s t | j�S rc )rM rq rC r r r r_ 7 s z NetworkConnectionError.__str__)NN) r, r- r. r/ rM r r> r_ rO r r rA r rp s ��rp c @ s e Zd ZdZdS )�InvalidWheelFilenamezInvalid wheel filename.Nr+ r r r r rt ; s rt c @ s e Zd ZdZdS )�UnsupportedWheelzUnsupported wheel.Nr+ r r r r ru ? s ru c @ s. e Zd ZdZeed�dd�Zed�dd�ZdS ) � InvalidWheelz Invalid (e.g. corrupt) wheel.��location�namec C s || _ || _d S rc rw )r@ rx ry r r r r> F s zInvalidWheel.__init__rB c C s d| j � d| j� d�S )NzWheel 'z ' located at z is invalid.)ry rx rC r r r r_ J s zInvalidWheel.__str__Nr` r r r r rv C s rv c @ s4 e Zd ZdZdeeedd�dd�Zed�dd �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. r N)�ireq�field�f_val�m_valr c C s || _ || _|| _|| _d S rc �r{ r| r} r~ )r@ r{ r| r} r~ r r r r> V s z MetadataInconsistent.__init__rB c C s$ d| j � d| j� d| j�d| j��S )N� Requested z has inconsistent z : expected z, but metadata has r rC r r r r_ ^ s "�z MetadataInconsistent.__str__r` r r r r rz N s � rz c @ s0 e Zd ZdZdedd�dd�Zed�dd �ZdS ) �MetadataInvalidzMetadata is invalid.r N)r{ r2 r c C s || _ || _d S rc �r{ r2 )r@ r{ r2 r r r r> h s zMetadataInvalid.__init__rB c C s d| j � d| j� �S )Nr� z has invalid metadata: r� rC r r r r_ l s zMetadataInvalid.__str__r` r r r r r� e s r� c sF e Zd ZdZdZeeeee dd�� fdd� Z ed�dd �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|�� d��t d�|�� t �d� }t� jdt|�� d|� �|d dd � || _|| _d S ) NzSee above for output.z[red][z lines of output][/] rI 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.�r6 r7 r8 r4 ) r � from_markup�lenr& r= r> r r� r� )r@ r� r� r� � output_promptrA r r r> u s ���� z$InstallationSubprocessError.__init__rB c C s | j � d| j� �S )Nz exited with )r� r� rC r r r r_ � s z#InstallationSubprocessError.__str__) r, r- r. r/ r1 rM �intr r r> r_ rO r r rA r r� p s � r� c s6 e Zd ZdZedd�� fdd� Zed�dd�Z� ZS ) �MetadataGenerationFailedzmetadata-generation-failedN)�package_detailsr 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� rA r r r> � s �z!MetadataGenerationFailed.__init__rB c C s dS )Nzmetadata generation failedr rC r r r r_ � s z MetadataGenerationFailed.__str__)r, r- r. r1 rM r> r_ rO r r rA r r� � s � r� c @ sJ e Zd ZdZdd�dd�Zddd�dd �Zed�d d �Zed�d d �Z dS )� HashErrorsz:Multiple HashError instances rolled into one for reportingNrB c C s g | _ d S rc )�errorsrC r r r r> � s zHashErrors.__init__� HashError�r2 r c C s | j �|� d S rc )r� �append)r@ r2 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 rc )�order��er r r �<lambda>� � z$HashErrors.__str__.<locals>.<lambda>)�keyc S s | j S rc rA r� r r r r� � r� c s s | ]}|� � V qd S rc )�body�rd r� r r r rf � s z%HashErrors.__str__.<locals>.<genexpr>r" rI )r� �sortr r� �head�extendr& )r@ �lines�cls� errors_of_clsr r r r_ � s zHashErrors.__str__c C s t | j�S rc )�boolr� rC r r r �__bool__� s zHashErrors.__bool__) r, r- r. r/ r> r� rM r_ r� r� r r r r r� � s r� c @ s\ e Zd ZU dZdZed ed< dZdZe ed< e d�d d �Z e d�d d �Z e d�d 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 �reqrI rg r� rB 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(). � )�_requirement_namerC r r r r� � s zHashError.bodyc C s | j � d| �� � �S )Nr" )r� r� rC r r r r_ � s 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� rM rC r r r r� � s zHashError._requirement_name)r, r- r. r/ r� r rN r� r� r� rM r� r_ r� r r r r r� � s r� c @ s 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- 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 ZdZdZdZedd�dd�Zed�d 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__rB c C sH ddl m} d }| jr4| jjr&| jjn t| jdd �}d�|p>d|| j�S )Nr )� FAVORITE_HASHr� z {} --hash={}:{}r� )�pip._internal.utils.hashesr� r� � is_direct� original_link�getattr�formatr� )r@ r� rS r r r r� s � � �zHashMissing.body) r, r- r. r/ r� r� rM 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� 1 s �r� c @ sZ e Zd ZdZdZdZeeee f eedf dd�dd�Z 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. � 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.r N)�allowed�gotsr 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> N s zHashMismatch.__init__rB c C s d| � � � d| �� � �S )Nr� z: )r� �_hash_comparisonrC r r r r� X s zHashMismatch.bodyc sn t dd�dd�}g }| j�� D ]D\}}||�� |�� fdd�|D �� |�d| j| �� � d�� 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 | gtd��S )Nz or)r r )r� r r r � hash_then_org s z3HashMismatch._hash_comparison.<locals>.hash_then_orc 3 s" | ]}d t � �� d|� �V qdS )z Expected � N)�nextr� �r r r rf o s z0HashMismatch._hash_comparison.<locals>.<genexpr>z Got r" )rM r� �itemsr� r� r� � hexdigestr& )r@ r� r� r� � expectedsr r� r r� [ s �z HashMismatch._hash_comparison) r, r- r. r/ r� r� r rM 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� v s r� c sF e Zd ZdZd eee eej dd�� fdd� Zed�dd �Z � Z S ) �!ConfigurationFileCouldNotBeLoadedz8When there are errors while loading a configuration file�could not be loadedN)r[ �fnamer2 r c s" t � �|� || _|| _|| _d S rc )r= r> r[ r� r2 )r@ r[ r� r2 rA r r r> ~ s z*ConfigurationFileCouldNotBeLoaded.__init__rB c C sF | j d k rd| j � d�}n | jd k s(t�d| j� d�}d| j� |� �S )Nz in �.z. r" zConfiguration file )r� r2 r< r[ )r@ � message_partr r r r_ � s z)ConfigurationFileCouldNotBeLoaded.__str__)r� NN) r, r- r. r/ rM r � configparser�Errorr> r_ rO r r rA 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 sd e Zd ZdZdZee dd�� fdd� Zee e d�dd ��Z e e e jef d d �d 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-environmentNr� c s6 |d krt 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.rW )r �!_DEFAULT_EXTERNALLY_MANAGED_ERRORr= r> )r@ r2 r7 rA r r r> � s �z%ExternallyManagedEnvironment.__init__rB c c s| z t j} W n tk r" d }Y nX t �| �\}}|d k rrd|� �V dD ]&}|�|�\}}}|sdqJd|� �V qJdV d S )NzError-)�-�_r� )�locale� LC_MESSAGES�AttributeError� getlocale� partition)�category�langr� �sepri �foundr r r �#_iter_externally_managed_error_keys� s z@ExternallyManagedEnvironment._iter_externally_managed_error_keys)�configr c C s� t jd d�}zX|j|dd� |d }| �� D ]4}t�t�� | || �W 5 Q R � W S Q R X q,W nT tk rx Y nB ttt j fk r� ddl m } t � |�}t jd||d� Y nX | d �S ) 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- r. r/ r1 r rM r> � staticmethodr r� � classmethodr �pathlib�Pathr� rO r r rA r r� � s �r� c s( e Zd ZdZddd�� fdd� Z� ZS )�UninstallMissingRecordzuninstall-no-record-filer N�� distributionr c sv |j }|r|dkr<|j� d|j� �}t�dd|� �df�}ntd|� d��}t� jtd|� ��d |j� d �|d � d S ) N�pipz==z,You might be able to recover from this via: z(pip install --force-reinstall --no-deps �greenz The package was installed by z3. You should check if it can uninstall the package.�Cannot uninstall zAThe package's contents are unknown: no RECORD file was found for r� �r6 r7 r8 )� installer�raw_name�versionr �assembler= r> )r@ r� r� �dep�hintrA r r r> � s � � �z UninstallMissingRecord.__init__�r, r- r. r1 r> rO r r rA r r� � s r� c s( e Zd ZdZddd�� fdd� Z� ZS )�LegacyDistutilsInstallz%uninstall-distutils-installed-packager Nr� c s t � jtd|� ��dd d� d S )Nr� z�It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall.r� )r= r> r )r@ r� rA r r r> s �z LegacyDistutilsInstall.__init__r� r r rA r r � s r )Rr/ r� r� r� �loggingr� r �sys� itertoolsr r r �typingr r r r r r r �pip._vendor.rich.consoler r r Zpip._vendor.rich.markupr �pip._vendor.rich.textr �hashlibr Zpip._vendor.requests.modelsr r �pip._internal.metadatar Z pip._internal.req.req_installr � getLoggerr, r� rM r� r r) � Exceptionr* r0 rP rQ rR rZ r\ ra rb rj rk rl rm rn ro rp rt ru rv rz r� r� r� r� r� r� r� r� r� r� r� r� r r� r� r� r r r r r �<module> s~ $ � v ). * :�I