/usr/local/lib/python3.9/site-packages/pip/_internal/metadata/__pycache__
a ���hR � @ s d dl mZ d dlZd dlZd dlZd dlZd dlmZmZm Z d dl mZ d dlm Z ddlmZmZmZmZmZ g d�Zd d �dd�Zd d �dd�ZG dd� de�Zejdd �dd��Zdd �dd�Zddd�dd�Zddd�dd�Zd ddd!�d"d#�Zd$dddd%�d&d'�ZdS )(� )�annotationsN)�Literal�Protocol�cast)� deprecated)� strtobool� )�BaseDistribution�BaseEnvironment�FilesystemWheel�MemoryWheel�Wheel) r r r r r �get_default_environment�get_environment�get_wheel_distribution�select_backend�bool)�returnc C st t jdkrdS t�tt��" tttj d ��W d � S 1 sB0 Y t jdk rZdS ddl } tt| jdd��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_METADATAN�r � Fr ) �sys�version_info� contextlib�suppress�KeyError� ValueErrorr r �os�environ�importlib.metadata�getattr�metadata�� importlib� r&