OwlCyberSecurity - MANAGER
Edit File: __init__.cpython-39.pyc
a �F�f� � @ s d dl Z d dlZd dlZd dlZd dlmZmZmZmZm Z d dl mZ ddlm Z mZmZmZmZ erzd dlmZmZ neZg d�Zed�d d �ZG dd� de�Zejdd �ed�dd��Zed�dd�Zeee ed�dd�Zee d�dd�Zeee d�dd�Ze eee d�dd�Z!dS )� N)� TYPE_CHECKING�List�Optional�Type�cast)� strtobool� )�BaseDistribution�BaseEnvironment�FilesystemWheel�MemoryWheel�Wheel)�Literal�Protocol) r r r r r �get_default_environment�get_environment�get_wheel_distribution�select_backend)�returnc C sf t �tt��" tttjd ��W d � S 1 s40 Y tj dk rLdS 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_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*). Z_PIP_USE_IMPORTLIB_METADATAN)� � Fr T) � contextlib�suppress�KeyError� ValueError�boolr �os�environ�sys�version_info�importlib.metadata�getattr�metadata�� importlib� r% �a/home/gouroczh/virtualenv/test/3.9/lib/python3.9/site-packages/pip/_internal/metadata/__init__.py�_should_use_importlib_metadata s 0 r'