Oe[ d dl mZ d dlZd dlZd dlZd dlZd dlmZmZm Z m Z d dlmZ d dl mZ ddlmZmZmZmZmZ erd dlmZ g d Zd$dZd%dZ G d de Zej d&d Zd'dZd(dZd)dZd*dZ d+d#Z!dS ), )annotationsN) TYPE_CHECKINGLiteralProtocolcast) deprecated) strtobool )BaseDistributionBaseEnvironmentFilesystemWheelMemoryWheelWheel)NormalizedName) r r r r r get_default_environmentget_environmentget_wheel_distributionselect_backendreturnboolc ^ t j dk rdS t j t t 5 t t t j d cddd S # 1 swxY w Y t j dk rdS ddl } t t | j dd S )a Whether to use the ``importlib.metadata`` or ``pkg_resources`` backend. By default, pip uses ``importlib.metadata`` on Python 3.11+, and ``pkg_resources`` otherwise. Up to Python 3.13, This can be overridden by a couple of ways: * If environment variable ``_PIP_USE_IMPORTLIB_METADATA`` is set, it dictates whether ``importlib.metadata`` is used, for Python <3.14. * On Python 3.11, 3.12 and 3.13, Python distributors can patch ``importlib.metadata`` to add a global constant ``_PIP_USE_IMPORTLIB_METADATA = False``. This makes pip use ``pkg_resources`` (unless the user set the aforementioned environment variable to *True*). On Python 3.14+, the ``pkg_resources`` backend cannot be used. ) T_PIP_USE_IMPORTLIB_METADATANr Fr ) sysversion_info contextlibsuppressKeyError ValueErrorr r osenvironimportlib.metadatagetattrmetadata importlibs q/builddir/build/BUILD/cloudlinux-venv-1.0.10/venv/lib/python3.11/site-packages/pip/_internal/metadata/__init__.py_should_use_importlib_metadatar+ s " 7""t Xz 2 2 J JIbj)FGHHIIJ J J J J J J J J J J J J J J J '!! u *,I4PPQQQs ,A++A/2A/Nonec t j dk rd S dd l} t | j d rd S t dddd d S ) Nr r r z7Using the pkg_resources metadata backend is deprecated.zpto use the default importlib.metadata backend, by unsetting the _PIP_USE_IMPORTLIB_METADATA environment variablez26.3i4 )reasonreplacementgone_inissue)r r r% hasattrr' r r( s r* )_emit_pkg_resources_deprecation_if_neededr3 ? st '!! y!#@AA H P c . e Zd ZU ded<