R`i H 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 ej2 d defd ZdefdZdeee defdZdede fdZdedede fdZde dedede fdZ!y) 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 sw Y nxY wt j dk ryddl } 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 /builddir/build/BUILDROOT/alt-python312-pip-23.3.1-3.el8.x86_64/opt/alt/python312/lib/python3.12/site-packages/pip/_internal/metadata/__init__.py_should_use_importlib_metadatar) sf Xz 2Ibjj)FGHI 3 2 2 '! **,I4PQQs %AAc 8 e Zd ZU ded<