1j ^ d dl Z d dlZd dlZd dlZd dlmZmZmZmZm Z d dl mZ ddlm Z mZmZmZmZ er d dlmZmZ neZg dZdefd Z G d de Z ej d defd ZdefdZdeee defdZdede fdZdedede fdZde dedede fdZ!dS ) N) TYPE_CHECKINGListOptionalTypecast) strtobool )BaseDistributionBaseEnvironmentFilesystemWheelMemoryWheelWheel)LiteralProtocol) r r r r r get_default_environmentget_environmentget_wheel_distributionselect_backendreturnc : 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_resourcess`` otherwise. 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, regardless of Python version. * On Python 3.11+, 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*). _PIP_USE_IMPORTLIB_METADATAN) Fr T) contextlibsuppressKeyError ValueErrorboolr osenvironsysversion_infoimportlib.metadatagetattrmetadata importlibs q/builddir/build/BUILD/cloudlinux-venv-1.0.11/venv/lib/python3.11/site-packages/pip/_internal/metadata/__init__.py_should_use_importlib_metadatar) s Xz 2 2 J JIbj)FGHHIIJ J J J J J J J J J J J J J J J '!!u *,I4PPQQQs ,AA Ac F e Zd ZU ded<