HEX

File: //usr/local/lib/python3.10/dist-packages/pip/_internal/__pycache__/exceptions.cpython-310.pyc
o

��h.q�@s�dZddlmZddlZddlZddlZddlZddlZddlZddl	Z	ddl
mZddlm
Z
mZmZddlmZmZddlmZddlmZdd	lmZmZmZdd
lmZddlmZer�ddlm Z dd
l!m"Z"m#Z#ddl$m%Z%ddl&m'Z'ddl(m)Z)e�*e+�Z,dodd�Z-dpdd�Z.Gdd �d e/�Z0Gd!d"�d"e0�Z1Gd#d$�d$e0�Z2Gd%d&�d&e0�Z3Gd'd(�d(e1�Z4Gd)d*�d*e1�Z5Gd+d,�d,e0�Z6Gd-d.�d.e3�Z7Gd/d0�d0e3�Z8Gd1d2�d2e3�Z9Gd3d4�d4e3�Z:Gd5d6�d6e0�Z;Gd7d8�d8e0�Z<Gd9d:�d:e0�Z=Gd;d<�d<e0�Z>Gd=d>�d>e0�Z?Gd?d@�d@e3�Z@GdAdB�dBe3�ZAGdCdD�dDe3�ZBGdEdF�dFe3�ZCGdGdH�dHe3�ZDGdIdJ�dJe1e3�ZEGdKdL�dLeEe3�ZFGdMdN�dNe3�ZGGdOdP�dPe3�ZHGdQdR�dReH�ZIGdSdT�dTeH�ZJGdUdV�dVeH�ZKGdWdX�dXeH�ZLGdYdZ�dZeH�ZMGd[d\�d\e3�ZNGd]d^�d^e2�ZOd_e	jP�d`�ZQGdadb�dbe1�ZRGdcdd�dde1�ZSGdedf�dfe1�ZTGdgdh�dhe1�ZUGdidj�dje1�ZVGdkdl�dle1�ZWGdmdn�dne1�ZXdS)qz�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.
�)�annotationsN)�Iterator)�chain�groupby�repeat)�
TYPE_CHECKING�Literal)�InvalidRequirement)�InvalidVersion)�Console�ConsoleOptions�RenderResult)�escape)�Text)�_Hash)�Request�Response)�BaseDistribution)�
_FileDownload)�InstallRequirement�s�str�return�boolcCst�d|�duS)Nz^[a-z]+(-[a-z]+)*$)�re�match)r�r�C/usr/local/lib/python3.10/dist-packages/pip/_internal/exceptions.py�_is_kebab_case*�r�
Text | str�consoler�prefix�indentrcCsJt|t�r|}n|�|�}|j|dd�|jd|��dd��|jdd��S)N�ignore)�overflow�
T)�allow_blank)�
isinstancer�
render_str�join�split)rr!r"r#�textrrr�_prefix_with_indent.s


��r-c@�eZdZdZdS)�PipErrorzThe base pip error.N��__name__�
__module__�__qualname__�__doc__rrrrr/?�r/csLeZdZUdZded<ddddd�d�fdd�Zddd�Zd 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`.
    r�	reference�errorN)�kindr7�	note_stmt�linkr9�Literal['error', 'warning']�
str | None�message�
str | Text�context�str | Text | None�	hint_stmtr:r;r�Nonecs~|durt|d�s
Jd��|j}t|�sJd��||_||_||_||_||_||_||_t	��
d|jj�d|j�d��dS)Nr7zerror reference not provided!z#error reference must be kebab-case!�<z: �>)
�hasattrr7rr9r>r@r:rBr;�super�__init__�	__class__r1)�selfr9r7r>r@rBr:r;�rIrrrHPs$zDiagnosticPipError.__init__c
Cs8d|jj�d|j�d|j�d|j�d|j�d|j�d�
S)NrDz(reference=z
, message=z
, context=z, note_stmt=z, hint_stmt=z)>)rIr1r7r>r@r:rB�rJrrr�__repr__ns������zDiagnosticPipError.__repr__r!r�optionsrr
ccsD�|jdkrdnd}d|�d|j�d|j�d�VdV|jsT|jdurIt|j|d|�d	�d|�d
�d�Vt|j|d|�d�d|�d
�d�Vnt|j|ddd�Vn|jV|jdurddV|jV|jdusn|jdurqdV|jdur�t|j|ddd�V|jdur�t|j|ddd�V|jdur�dVd|j��VdSdS)Nr8�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: )	r9r7�
ascii_onlyr@r-r>r:rBr;)rJr!rN�colourrrr�__rich_console__ys`�


�


�
�

�
�
�z#DiagnosticPipError.__rich_console__)r9r<r7r=r>r?r@rArBrAr:rAr;r=rrC�rr)r!rrNrrr
)	r1r2r3r4�__annotations__rHrMrU�
__classcell__rrrKrr6Cs

�
r6c@r.)�ConfigurationErrorz"General exception in configurationNr0rrrrrY�r5rYc@r.)�InstallationErrorz%General exception during installationNr0rrrrrZ�r5rZc�&eZdZdZdZd	�fdd�Z�ZS)
�MissingPyProjectBuildRequireszNRaised when pyproject.toml has `build-system`, but no `build-system.requires`.z'missing-pyproject-build-system-requires�packagerrrCcs*t�jdt|���td�dtd�d�dS)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.�r>r@r:rB�rGrHrr)rJr]rKrrrH�s�
�z&MissingPyProjectBuildRequires.__init__)r]rrrC�r1r2r3r4r7rHrXrrrKrr\��r\cs&eZdZdZdZd
�fdd	�Z�ZS)�InvalidPyProjectBuildRequiresz>Raised when pyproject.toml an invalid `build-system.requires`.z'invalid-pyproject-build-system-requiresr]r�reasonrrCcs0t�jdt|���td|���dtd�d�dS)Nr^zKThis package has an invalid `build-system.requires` key in pyproject.toml.
r_r`rarb)rJr]rfrKrrrH�s��
�z&InvalidPyProjectBuildRequires.__init__)r]rrfrrrCrcrrrKrre�rdrec@�$eZdZdZd
dd	�Zdd
d�ZdS)�NoneMetadataErrora4Raised 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_namerrrCcC�||_||_dS)z�
        :param dist: A Distribution object.
        :param metadata_name: The name of the metadata being accessed
            (can be "METADATA" or "PKG-INFO").
        N)rirj)rJrirjrrrrH�s

zNoneMetadataError.__init__cC�d|j�d|j��S)NzNone z" metadata found for distribution: )rjrirLrrr�__str__�szNoneMetadataError.__str__N)rirrjrrrCrV�r1r2r3r4rHrmrrrrrh�s

rhc@seZdZdZddd�ZdS)�UserInstallationInvalidzBA --user install is requested on an environment without user site.rrcC�dS)Nz$User base directory is not specifiedrrLrrrrm�zUserInstallationInvalid.__str__NrV)r1r2r3r4rmrrrrro�sroc@seZdZddd�ZdS)�InvalidSchemeCombinationrrcCs6d�dd�|jdd�D��}d|�d|jd�d�S)N�, css�|]}t|�VqdS�N)r)�.0�arrr�	<genexpr>��z3InvalidSchemeCombination.__str__.<locals>.<genexpr>���zCannot set z and z	 together)r*�args)rJ�beforerrrrmsz InvalidSchemeCombination.__str__NrV)r1r2r3rmrrrrrrsrrc@r.)�DistributionNotFoundzCRaised when a distribution cannot be found to satisfy a requirementNr0rrrrr|r5r|c@r.)�RequirementsFileParseErrorzDRaised when a general error occurs parsing a requirements file line.Nr0rrrrr}r5r}c@r.)�BestVersionAlreadyInstalledzNRaised when the most up-to-date version of a package is already
    installed.Nr0rrrrr~r5r~c@r.)�
BadCommandz0Raised when virtualenv or a command is not foundNr0rrrrrr5rc@r.)�CommandErrorz7Raised when there is an error in command-line argumentsNr0rrrrr�r5r�c@r.)�PreviousBuildDirErrorz:Raised when there's a previous conflicting build directoryNr0rrrrr�!r5r�cs2eZdZdZ		dd�fdd�
Zdd
d�Z�ZS)�NetworkConnectionErrorzHTTP connection errorN�	error_msgr�response�Response | None�request�Request | NonerrCcsJ||_||_||_|jdur|jst|d�r|jj|_t��|||�dS)zc
        Initialize NetworkConnectionError with  `request` and `response`
        objects.
        Nr�)r�r�r�rFrGrH)rJr�r�r�rKrrrH(s

��
zNetworkConnectionError.__init__cC�
t|j�Srt)rr�rLrrrrm=�
zNetworkConnectionError.__str__)NN)r�rr�r�r�r�rrCrV�r1r2r3r4rHrmrXrrrKrr�%s�r�c@r.)�InvalidWheelFilenamezInvalid wheel filename.Nr0rrrrr�Ar5r�c@r.)�UnsupportedWheelzUnsupported wheel.Nr0rrrrr�Er5r�c@s$eZdZdZddd�Zddd	�Zd
S)
�InvalidWheelzInvalid (e.g. corrupt) wheel.�locationr�namecC�||_||_dSrt)r�r�)rJr�r�rrrrHL�
zInvalidWheel.__init__rcCsd|j�d|j�d�S)NzWheel 'z
' located at z is invalid.)r�r�rLrrrrmPszInvalidWheel.__str__N)r�rr�rrVrnrrrrr�I�
r�c@s$eZdZdZdd
d�Zddd
�ZdS)�MetadataInconsistentaBuilt 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�fieldr�f_val�m_valrrCcCs||_||_||_||_dSrt�r�r�r�r�)rJr�r�r�r�rrrrH\s
zMetadataInconsistent.__init__cCs$d|j�d|j�d|j�d|j��S)N�
Requested z has inconsistent z: expected z, but metadata has r�rLrrrrmds���zMetadataInconsistent.__str__N)
r�rr�rr�rr�rrrCrVrnrrrrr�Ts
r�c@rg)�MetadataInvalidzMetadata is invalid.r�rr8rrrCcCr�rt�r�r8)rJr�r8rrrrHnr�zMetadataInvalid.__init__cCrl)Nr�z has invalid metadata: r�rLrrrrmr�zMetadataInvalid.__str__N)r�rr8rrrCrVrnrrrrr�kr�r�cs0eZdZdZdZd�fdd�Zdd
d�Z�ZS)�InstallationSubprocessErrorzA subprocess call failed.zsubprocess-exited-with-error�command_descriptionr�	exit_code�int�output_lines�list[str] | NonerrCcst|dur	td�}nt�dt|��d��td�|��t�d�}t�jdt|��d|��|ddd	�||_||_dS)
NzSee above for output.z[red][z lines of output][/]
rRz[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@rBr:)	r�from_markup�lenr*rGrHrr�r�)rJr�r�r��
output_promptrKrrrH{s$
�����
z$InstallationSubprocessError.__init__cCs|j�d|j��S)Nz
 exited with )r�r�rLrrrrm�sz#InstallationSubprocessError.__str__)r�rr�r�r�r�rrCrV)r1r2r3r4r7rHrmrXrrrKrr�vs
 r�cs,eZdZdZd
�fdd�Zddd	�Z�ZS)�MetadataGenerationFailedzmetadata-generation-failed�package_detailsrrrCcs tt|�jdt|�ddd�dS)Nz4Encountered error while generating package metadata.zSee above for details.r_r�)rGr�rHr)rJr�rKrrrH�s

�z!MetadataGenerationFailed.__init__cCrp)Nzmetadata generation failedrrLrrrrm�rqz MetadataGenerationFailed.__str__)r�rrrCrV)r1r2r3r7rHrmrXrrrKrr��sr�c@s8eZdZdZddd�Zddd	�Zddd�Zddd�ZdS)�
HashErrorsz:Multiple HashError instances rolled into one for reportingrrCcCs
g|_dSrt)�errorsrLrrrrH�r�zHashErrors.__init__r8�	HashErrorcCs|j�|�dSrt)r��append)rJr8rrrr��rzHashErrors.appendrcCsbg}|jjdd�d�t|jdd��D]\}}|�|j�|�dd�|D��q|r/d�|�SdS)	NcS�|jSrt)�order��errr�<lambda>��z$HashErrors.__str__.<locals>.<lambda>)�keycSr�rtrKr�rrrr��r�css�|]}|��VqdSrt)�body�rur�rrrrw�rxz%HashErrors.__str__.<locals>.<genexpr>r&rR)r��sortrr��head�extendr*)rJ�lines�cls�
errors_of_clsrrrrm�s
zHashErrors.__str__rcCr�rt)rr�rLrrr�__bool__�r�zHashErrors.__bool__N�rrC)r8r�rrCrV)rr)r1r2r3r4rHr�rmr�rrrrr��s



r�c@sLeZdZUdZdZded<dZdZded<ddd�Zdd
d�Z	ddd�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.

    NzInstallRequirement | None�reqrRryr�r�rrcCsd|����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_namerLrrrr��s
zHashError.bodycCs|j�d|����S)Nr&)r�r�rLrrrrm�r�zHashError.__str__cCs|jrt|j�SdS)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�rrLrrrr��szHashError._requirement_namerV)r1r2r3r4r�rWr�r�r�rmr�rrrrr��s


r�c@�eZdZdZdZdZdS)�VcsHashUnsupported�uA hash was provided for a version-control-system-based requirement, but
    we don't have a method for hashing those.rzlCan't verify hashes for these requirements because we don't have a way to hash version control repositories:N�r1r2r3r4r�r�rrrrr���
�r�c@r�)�DirectoryUrlHashUnsupportedr��zUCan't verify hashes for these file:// requirements because they point to directories:Nr�rrrrr�r�r�c@s,eZdZdZdZdZd
dd	�Zdd
d�ZdS)�HashMissingz2A hash was needed for a requirement but is absent.�awHashes 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_hashrrrCcCs
||_dS)zq
        :param gotten_hash: The hash of the (possibly malicious) archive we
            just downloaded
        N)r�)rJr�rrrrHs
zHashMissing.__init__cCsHddlm}d}|jr|jjr|jjnt|jdd�}d�|pd||j�S)Nr)�
FAVORITE_HASHr�z    {} --hash={}:{}r�)�pip._internal.utils.hashesr�r��	is_direct�
original_link�getattr�formatr�)rJr�r]rrrr�"s
���zHashMissing.bodyN)r�rrrCrV)r1r2r3r4r�r�rHr�rrrrr�
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�rrrrr�7r�r�c@s6eZdZdZdZdZdd
d�Zdd
d�Zddd�ZdS)�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�dict[str, list[str]]�gots�dict[str, _Hash]rrCcCrk)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�)rJr�r�rrrrHTs
zHashMismatch.__init__rcCsd|���d|����S)Nr��:
)r��_hash_comparisonrLrrrr�^szHashMismatch.bodycshddd�}g}|j��D]"\}}||��|��fdd�|D��|�d	|j|���d
��qd
�|�S)
aE
        Return a comparison of actual and expected hash values.

        Example::

               Expected sha256 abcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcde
                            or 123451234512345123451234512345123451234512345
                    Got        bcdefbcdefbcdefbcdefbcdefbcdefbcdefbcdefbcdef

        �	hash_namerr�
chain[str]cSst|gtd��S)Nz    or)rr)r�rrr�hash_then_ormsz3HashMismatch._hash_comparison.<locals>.hash_then_orc3s$�|]
}dt���d|��VqdS)z        Expected � N)�nextr��r"rrrwus�"z0HashMismatch._hash_comparison.<locals>.<genexpr>z             Got        r&N)r�rrr�)r��itemsr�r�r��	hexdigestr*)rJr�r�r��	expectedsrr�rr�as
�
zHashMismatch._hash_comparisonN)r�r�r�r�rrCrV)	r1r2r3r4r�r�rHr�r�rrrrr�Bs	�


r�c@r.)�UnsupportedPythonVersionzMUnsupported python version according to Requires-Python package
    metadata.Nr0rrrrr�|r5r�cs4eZdZdZ			dd�fdd
�
Zddd�Z�ZS)�!ConfigurationFileCouldNotBeLoadedz8When there are errors while loading a configuration file�could not be loadedNrfr�fnamer=r8�configparser.Error | NonerrCcs"t��|�||_||_||_dSrt)rGrHrfr�r8)rJrfr�r8rKrrrH�s
z*ConfigurationFileCouldNotBeLoaded.__init__cCsF|jdur
d|j�d�}n|jdusJ�d|j�d�}d|j�|��S)Nz in �.z.
r&zConfiguration file )r�r8rf)rJ�message_partrrrrm�s

z)ConfigurationFileCouldNotBeLoaded.__str__)r�NN)rfrr�r=r8r�rrCrVr�rrrKrr��s�r�zThe 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.
csBeZdZdZdZd�fdd�Zedd
d��Zeddd��Z	�Z
S)�ExternallyManagedEnvironmentaPThe 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``.
    zexternally-managed-environmentr8r=rrCcs6|dur	tt�}nt|�}t�jd|dtd�d�dS)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.ra)r�!_DEFAULT_EXTERNALLY_MANAGED_ERRORrGrH)rJr8r@rKrrrH�s

�z%ExternallyManagedEnvironment.__init__�
Iterator[str]ccs|�ztj}Wntyd}Ynwt�|�\}}|dur9d|��VdD]}|�|�\}}}|s2q%d|��Vq%dVdS)NzError-)�-�_�Error)�locale�LC_MESSAGES�AttributeError�	getlocale�	partition)�category�langr��sepr{�foundrrr�#_iter_externally_managed_error_keys�s�
�
z@ExternallyManagedEnvironment._iter_externally_managed_error_keys�config�pathlib.Path | strc
Cs�tjdd�}z5|j|dd�|d}|��D] }t�t��|||�Wd�WS1s1wYqW|d�StyGY|d�Stttj	fyiddl
m}t�
|�}tjd||d�Y|d�Sw)	N)�
interpolationzutf-8)�encodingzexternally-managedr)�VERBOSEzFailed to read %s)�exc_info)�configparser�ConfigParser�readr��
contextlib�suppress�KeyError�OSError�UnicodeDecodeError�ParsingError�pip._internal.utils._logr�logger�isEnabledFor�warning)r�r��parser�sectionr�rrrrr�from_config�s&
(��
��
�z(ExternallyManagedEnvironment.from_config)r8r=rrC)rr�)r�r�rr�)r1r2r3r4r7rH�staticmethodr��classmethodrrXrrrKrr��s	r�c�"eZdZdZd�fdd�Z�ZS)	�UninstallMissingRecordzuninstall-no-record-file�distributionrrrCcsv|j}|r	|dkr|j�d|j��}t�dd|��df�}ntd|�d��}t�jtd|���d	|j�d
�|d�dS)N�pipz==z,You might be able to recover from this via: z(pip install --force-reinstall --no-deps �greenzThe 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��r>r@rB)�	installer�raw_name�versionr�assemblerGrH)rJrr�dep�hintrKrrrH�s"�
��
�zUninstallMissingRecord.__init__�rrrrC�r1r2r3r7rHrXrrrKrr��rcr)	�LegacyDistutilsInstallz%uninstall-distutils-installed-packagerrrrCcs t�jtd|���ddd�dS)Nrz�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)rGrHr)rJrrKrrrHs

�zLegacyDistutilsInstall.__init__r!r"rrrKrr$r#r$cs"eZdZdZd
�fdd	�Z�ZS)�InvalidInstalledPackagezinvalid-installed-packagerir�invalid_exc�#InvalidRequirement | InvalidVersionrrCcsn|j}t|t�rd}nd}t�jtd|�d�|rd|�d�ndd|�d|jd	���d
|�d�dd
�dS)N�requirementrz!Cannot process installed package r�zin rRzbecause it has an invalid r�rz.Starting with pip 24.1, packages with invalid zs can not be processed.z,To proceed this package must be uninstalled.r)�installed_locationr(r	rGrHrrz)rJrir&r)�invalid_typerKrrrHs"

����
�z InvalidInstalledPackage.__init__)rirr&r'rrCr"rrrKrr%r#r%cr[)
�IncompleteDownloadErrorzaRaised when the downloader receives fewer bytes than advertised
    in the Content-Length header.zincomplete-download�downloadrrrCcs�ddlm}|jdus
J�||j��d||j���}|jr)d|jd�d�}d}nd}d	}td
|�d|�d��}t�j|d
|jj	��|dd�dS)Nr)�format_size�/zafter r�z
 attempts z7Use --resume-retries to configure resume attempt limit.rRz>Consider using --resume-retries to enable download resumption.zDownload failed z(because not enough bytes were received (�)zURL: z4This is an issue with network connectivity, not pip.r�)
�pip._internal.utils.miscr-�size�bytes_received�
reattemptsrrGrHr;�redacted_url)rJr,r-�download_status�retry_statusr r>rKrrrH6s(���
�z IncompleteDownloadError.__init__)r,rrrCrcrrrKrr+0sr+cs&eZdZdZdZd�fdd�Z�ZS)�ResolutionTooDeepErrorzHRaised when the dependency resolver exceeds the maximum recursion depth.zresolution-too-deeprrCcst�jddddd�dS)Nz,Dependency resolution exceeded maximum depthzpPip cannot resolve the current dependencies as the dependency graph is too complex for pip to solve efficiently.zqTry adding lower bounds to constrain your dependencies, for example: 'package>=2.0.0' instead of just 'package'. z_https://pip.pypa.io/en/stable/topics/dependency-resolution/#handling-resolution-too-deep-errors)r>r@rBr;)rGrHrLrKrrrHWs
�zResolutionTooDeepError.__init__r�rcrrrKrr7Rrdr7cr)	�InstallWheelBuildErrorzfailed-wheel-build-for-install�failed�list[InstallRequirement]rrCcs&t�jdd�dd�|D��dd�dS)NzIFailed to build installable wheels for some pyproject.toml based projectsrscss�|]}|jVqdSrt)r�)ru�rrrrrwos�z2InstallWheelBuildError.__init__.<locals>.<genexpr>r)rGrHr*)rJr9rKrrrHis

�zInstallWheelBuildError.__init__)r9r:rrCr"rrrKrr8fr#r8)rrrr)
rr r!rr"rr#rrr)Yr4�
__future__rrrr��logging�pathlibr�sys�collections.abcr�	itertoolsrrr�typingrr�"pip._vendor.packaging.requirementsr	�pip._vendor.packaging.versionr
�pip._vendor.rich.consolerrr
�pip._vendor.rich.markupr�pip._vendor.rich.textr�hashlibr�pip._vendor.requests.modelsrr�pip._internal.metadatar�pip._internal.network.downloadr�pip._internal.req.req_installr�	getLoggerr1rrr-�	Exceptionr/r6rYrZr\rerhrorrr|r}r~rr�r�r�r�r�r�r�r�r�r�r�r�r�r�r�r�r�r�r�r"r�r�rr$r%r+r7r8rrrr�<module>s�


v).*:�I"