2bi Z S SK r S SKrS SKrS SKrS SKJrJrJrJrJ r S SK Jr SSKJ r JrJrJrJr \( a S SKJrJr O\r/ SQrS\4S jr " S S\5 r\R2 " SS9S\4S j5 rS\4S jrS\\\ S\4S jrS\S\ 4S jrS\S\S\ 4S jrS\ S\S\S\ 4S jr!g) N) TYPE_CHECKINGListOptionalTypecast) strtobool )BaseDistributionBaseEnvironmentFilesystemWheelMemoryWheelWheel)LiteralProtocol) r r r r r get_default_environmentget_environmentget_wheel_distributionselect_backendreturnc 2 [ R " [ [ 5 [ [ [ R S 5 5 sSSS5 $ ! , ( d f O= f[ R S: a gSSK n [ [ U R SS5 5 $ )ak 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-python313-pip-23.3.1-3.el8.x86_64/opt/alt/python313/lib/python3.13/site-packages/pip/_internal/metadata/__init__.py_should_use_importlib_metadatar) sf Xz 2Ibjj)FGHI 3 2 2 '! **,I4PQQs %A Ac @ \ rS rSr% S\S' \\ \S' \\ \S' Srg)Backend4 z%Literal["importlib", "pkg_resources"]NAMEDistributionEnvironment N) __name__ __module____qualname____firstlineno____annotations__r r r __static_attributes__r0 r( r+ r+ 4 s 11'((o&&r7