Current File : //lib/python3.9/site-packages/pip/_vendor/urllib3/util/__pycache__/retry.cpython-39.pyc
a

[��f�S�@s�ddlmZddlZddlZddlZddlZddlZddlmZddl	m
Z
ddlmZm
Z
mZmZmZmZmZddlmZe�e�Zedgd	��Ze�ZGd
d�de�Ze�e�Gdd
�d
e��Zed�e_dS)�)�absolute_importN)�
namedtuple)�	takewhile�)�ConnectTimeoutError�
InvalidHeader�
MaxRetryError�
ProtocolError�
ProxyError�ReadTimeoutError�
ResponseError)�six�RequestHistory)�method�url�error�status�redirect_locationc@s@eZdZedd��Zejdd��Zedd��Zejdd��ZdS)�
_RetryMetacCst�dt�|jS�Nz}Using 'Retry.DEFAULT_METHOD_WHITELIST' is deprecated and will be removed in v2.0. Use 'Retry.DEFAULT_ALLOWED_METHODS' instead��warnings�warn�DeprecationWarning�DEFAULT_ALLOWED_METHODS��cls�r�B/usr/lib/python3.9/site-packages/pip/_vendor/urllib3/util/retry.py�DEFAULT_METHOD_WHITELIST$s
�z#_RetryMeta.DEFAULT_METHOD_WHITELISTcCst�dt�||_dSrr�r�valuerrrr-s
�cCst�dt�|jS�Nz�Using 'Retry.DEFAULT_REDIRECT_HEADERS_BLACKLIST' is deprecated and will be removed in v2.0. Use 'Retry.DEFAULT_REMOVE_HEADERS_ON_REDIRECT' instead�rrr�"DEFAULT_REMOVE_HEADERS_ON_REDIRECTrrrr�"DEFAULT_REDIRECT_HEADERS_BLACKLIST6s
�z-_RetryMeta.DEFAULT_REDIRECT_HEADERS_BLACKLISTcCst�dt�||_dSr"r#r rrrr%?s
�N)�__name__�
__module__�__qualname__�propertyr�setterr%rrrrr#s


rcs�eZdZdZegd��Zegd��Zedg�ZdZdddddde	ddd	d	dd	e	e	fd
d�Z
dd
�Zed-dd��Z
dd�Zdd�Zdd�Zd.dd�Zdd�Zd/dd�Zdd�Zdd�Zd d!�Zd0d#d$�Zd%d&�Zd1d'd(�Zd)d*�Z�fd+d,�Z�ZS)2�RetryaBRetry configuration.

    Each retry attempt will create a new Retry object with updated values, so
    they can be safely reused.

    Retries can be defined as a default for a pool::

        retries = Retry(connect=5, read=2, redirect=5)
        http = PoolManager(retries=retries)
        response = http.request('GET', 'http://example.com/')

    Or per-request (which overrides the default for the pool)::

        response = http.request('GET', 'http://example.com/', retries=Retry(10))

    Retries can be disabled by passing ``False``::

        response = http.request('GET', 'http://example.com/', retries=False)

    Errors will be wrapped in :class:`~urllib3.exceptions.MaxRetryError` unless
    retries are disabled, in which case the causing exception will be raised.

    :param int total:
        Total number of retries to allow. Takes precedence over other counts.

        Set to ``None`` to remove this constraint and fall back on other
        counts.

        Set to ``0`` to fail on the first retry.

        Set to ``False`` to disable and imply ``raise_on_redirect=False``.

    :param int connect:
        How many connection-related errors to retry on.

        These are errors raised before the request is sent to the remote server,
        which we assume has not triggered the server to process the request.

        Set to ``0`` to fail on the first retry of this type.

    :param int read:
        How many times to retry on read errors.

        These errors are raised after the request was sent to the server, so the
        request may have side-effects.

        Set to ``0`` to fail on the first retry of this type.

    :param int redirect:
        How many redirects to perform. Limit this to avoid infinite redirect
        loops.

        A redirect is a HTTP response with a status code 301, 302, 303, 307 or
        308.

        Set to ``0`` to fail on the first retry of this type.

        Set to ``False`` to disable and imply ``raise_on_redirect=False``.

    :param int status:
        How many times to retry on bad status codes.

        These are retries made on responses, where status code matches
        ``status_forcelist``.

        Set to ``0`` to fail on the first retry of this type.

    :param int other:
        How many times to retry on other errors.

        Other errors are errors that are not connect, read, redirect or status errors.
        These errors might be raised after the request was sent to the server, so the
        request might have side-effects.

        Set to ``0`` to fail on the first retry of this type.

        If ``total`` is not set, it's a good idea to set this to 0 to account
        for unexpected edge cases and avoid infinite retry loops.

    :param iterable allowed_methods:
        Set of uppercased HTTP method verbs that we should retry on.

        By default, we only retry on methods which are considered to be
        idempotent (multiple requests with the same parameters end with the
        same state). See :attr:`Retry.DEFAULT_ALLOWED_METHODS`.

        Set to a ``False`` value to retry on any verb.

        .. warning::

            Previously this parameter was named ``method_whitelist``, that
            usage is deprecated in v1.26.0 and will be removed in v2.0.

    :param iterable status_forcelist:
        A set of integer HTTP status codes that we should force a retry on.
        A retry is initiated if the request method is in ``allowed_methods``
        and the response status code is in ``status_forcelist``.

        By default, this is disabled with ``None``.

    :param float backoff_factor:
        A backoff factor to apply between attempts after the second try
        (most errors are resolved immediately by a second try without a
        delay). urllib3 will sleep for::

            {backoff factor} * (2 ** ({number of total retries} - 1))

        seconds. If the backoff_factor is 0.1, then :func:`.sleep` will sleep
        for [0.0s, 0.2s, 0.4s, ...] between retries. It will never be longer
        than :attr:`Retry.BACKOFF_MAX`.

        By default, backoff is disabled (set to 0).

    :param bool raise_on_redirect: Whether, if the number of redirects is
        exhausted, to raise a MaxRetryError, or to return a response with a
        response code in the 3xx range.

    :param bool raise_on_status: Similar meaning to ``raise_on_redirect``:
        whether we should raise an exception, or return a response,
        if status falls in ``status_forcelist`` range and retries have
        been exhausted.

    :param tuple history: The history of the request encountered during
        each call to :meth:`~Retry.increment`. The list is in the order
        the requests occurred. Each list item is of class :class:`RequestHistory`.

    :param bool respect_retry_after_header:
        Whether to respect Retry-After header on status codes defined as
        :attr:`Retry.RETRY_AFTER_STATUS_CODES` or not.

    :param iterable remove_headers_on_redirect:
        Sequence of headers to remove from the request when a response
        indicating a redirect is returned before firing off the redirected
        request.
    )ZHEADZGETZPUTZDELETEZOPTIONSZTRACE)i�i�i�Z
Authorization�x�
NrTcCs�|tur,|turtd��tjdtdd�|}|tur:|j}|turH|j}||_||_||_	||_
||_|dusv|dur~d}d}
||_|p�t
�|_||_|	|_|
|_||_|p�t�|_|
|_tdd�|D��|_dS)	NzoUsing both 'allowed_methods' and 'method_whitelist' together is not allowed. Instead only use 'allowed_methods'�lUsing 'method_whitelist' with Retry is deprecated and will be removed in v2.0. Use 'allowed_methods' insteadr)�
stacklevelFrcSsg|]}|���qSr)�lower)�.0�hrrr�
<listcomp>�z"Retry.__init__.<locals>.<listcomp>)�_Default�
ValueErrorrrrrr$�total�connect�readr�other�redirect�set�status_forcelist�allowed_methods�backoff_factor�raise_on_redirect�raise_on_status�tuple�history�respect_retry_after_header�	frozenset�remove_headers_on_redirect)�selfr7r8r9r;rr:r>r=r?r@rArCrDrF�method_whitelistrrr�__init__�sD���zRetry.__init__cKs�t|j|j|j|j|j|j|j|j|j	|j
|j|j|j
d�
}d|vrxd|vrxd|jvrnt�dt�|j|d<n
|j|d<|�|�t|�fi|��S)N)
r7r8r9r;rr:r=r?r@rArCrFrDrHr>r.)�dictr7r8r9r;rr:r=r?r@rArCrFrD�__dict__rrrr>�update�type)rG�kw�paramsrrr�news2�
�

z	Retry.newcCsR|dur|dur|n|j}t|t�r(|St|�o2d}|||d�}t�d||�|S)z3Backwards-compatibility for the old retries format.N)r;z!Converted retries value: %r -> %r)�DEFAULT�
isinstancer+�bool�log�debug)rZretriesr;�defaultZnew_retriesrrr�from_intBs
zRetry.from_intcCsFtttdd�t|j����}|dkr(dS|jd|d}t|j|�S)zIFormula for computing the current backoff

        :rtype: float
        cSs
|jduS)N)r)�xrrr�<lambda>Xr4z(Retry.get_backoff_time.<locals>.<lambda>�rr)�len�listr�reversedrCr?�min�BACKOFF_MAX)rGZconsecutive_errors_lenZ
backoff_valuerrr�get_backoff_timePs��zRetry.get_backoff_timecCs�t�d|�rt|�}n`tj�|�}|dur6td|��|ddur^|dd�d|dd�}tj�|�}|t��}|dkr�d}|S)Nz^\s*[0-9]+\s*$zInvalid Retry-After header: %s�	)rr-r)	�re�match�int�emailZutilsZparsedate_tzrZ	mktime_tz�time)rG�retry_afterZsecondsZretry_date_tupleZ
retry_daterrr�parse_retry_afteras
zRetry.parse_retry_aftercCs |�d�}|durdS|�|�S)z(Get the value of Retry-After in seconds.zRetry-AfterN)Z	getheaderrh�rG�responsergrrr�get_retry_afterxs
zRetry.get_retry_aftercCs |�|�}|rt�|�dSdS)NTF)rkrf�sleeprirrr�sleep_for_retry�s


zRetry.sleep_for_retrycCs"|��}|dkrdSt�|�dS)Nr)r`rfrl)rGZbackoffrrr�_sleep_backoff�szRetry._sleep_backoffcCs(|jr|r|�|�}|rdS|��dS)aBSleep between retry attempts.

        This method will respect a server's ``Retry-After`` response header
        and sleep the duration of the time requested. If that is not present, it
        will use an exponential backoff. By default, the backoff factor is 0 and
        this method will return immediately.
        N)rDrmrn)rGrjZsleptrrrrl�s
	

zRetry.sleepcCst|t�r|j}t|t�S)zzErrors when we're fairly sure that the server did not receive the
        request, so it should be safe to retry.
        )rRr
Zoriginal_errorr�rG�errrrr�_is_connection_error�s
zRetry._is_connection_errorcCst|ttf�S)zErrors that occur after the request has been started, so we should
        assume that the server began processing it.
        )rRrr	rorrr�_is_read_error�szRetry._is_read_errorcCs<d|jvrt�dt�|j}n|j}|r8|��|vr8dSdS)zyChecks if a given HTTP method should be retried upon, depending if
        it is included in the allowed_methods
        rHr.FT)rKrrrrHr>�upper)rGrr>rrr�_is_method_retryable�s
�zRetry._is_method_retryableFcCs<|�|�sdS|jr"||jvr"dS|jo:|jo:|o:||jvS)awIs this method/status code retryable? (Based on allowlists and control
        variables such as the number of total retries to allow, whether to
        respect the Retry-After header, whether this header is present, and
        whether the returned status code is on the list of status codes to
        be retried upon on the presence of the aforementioned header)
        FT)rtr=r7rD�RETRY_AFTER_STATUS_CODES)rGr�status_codeZhas_retry_afterrrr�is_retry�s
���zRetry.is_retrycCs>|j|j|j|j|j|jf}ttd|��}|s2dSt|�dkS)zAre we out of retries?NFr)	r7r8r9r;rr:r\�filterr^)rGZretry_countsrrr�is_exhausted�s�zRetry.is_exhaustedc	Cs�|jdur |r t�t|�||��|j}|dur6|d8}|j}|j}	|j}
|j}|j}d}
d}d}|r�|�	|�r�|dur�t�t|�||��n|dur�|d8}n�|r�|�
|�r�|	dus�|�|�s�t�t|�||��n|	dur�|	d8}	n�|r�|dur�|d8}nr|�r.|���r.|
du�r|
d8}
d}
|��}|j}n<t
j}
|�rj|j�rj|du�rT|d8}t
jj|jd�}
|j}|jt|||||�f}|j|||	|
|||d�}|���r�t|||�p�t
|
���t�d||�|S)	a�Return a new Retry object with incremented retry counters.

        :param response: A response object, or None, if the server did not
            return a response.
        :type response: :class:`~urllib3.response.HTTPResponse`
        :param Exception error: An error encountered during the request, or
            None if the response was received successfully.

        :return: A new ``Retry`` object.
        FNrZ�unknownztoo many redirects)rv)r7r8r9r;rr:rCz$Incremented Retry for (url='%s'): %r)r7r
ZreraiserMr8r9r;rr:rqrrrtZget_redirect_locationrZ
GENERIC_ERRORZSPECIFIC_ERROR�formatrCrrPryrrTrU)rGrrrjrZ_poolZ_stacktracer7r8r9r;Zstatus_countr:�causerrrCZ	new_retryrrr�	increment�sl




��

zRetry.incrementcCsdjt|�|d�S)Nz|{cls.__name__}(total={self.total}, connect={self.connect}, read={self.read}, redirect={self.redirect}, status={self.status}))rrG)r{rM)rGrrr�__repr__Ds��zRetry.__repr__csN|dkrt�dt�|jSzttt|�|�WStyHtt|�YS0dS)NrHr.)rrrr>�getattr�superr+�AttributeError)rG�item��	__class__rr�__getattr__Js�zRetry.__getattr__)TN)N)N)F)NNNNNN)r&r'r(�__doc__rErrur$r_r5rIrP�classmethodrWr`rhrkrmrnrlrqrrrtrwryr}r~r��
__classcell__rrr�rr+Is^
�
�
=$




�
^r+�) Z
__future__rreZloggingrbrfr�collectionsr�	itertoolsr�
exceptionsrrrr	r
rrZpackagesr
Z	getLoggerr&rTr�objectr5rMrZ
add_metaclassr+rQrrrr�<module>s,$	
�&