OwlCyberSecurity - MANAGER
Edit File: __init__.cpython-311.pyc
� p�Fh[ � �\ � d dl Z d dlZd dlZd dlZd dlmZmZmZmZm Z m Z d dlmZ d dl mZ ddlmZmZmZmZmZ g d�Zdefd �Zdd �Z G d� de� � Z ej d� � � defd�� � Zdefd�Zdeee defd�Zdedefd�Zdededefd�Z de!dededefd�Z"dS )� N)�List�Literal�Optional�Protocol�Type�cast)� deprecated)� strtobool� )�BaseDistribution�BaseEnvironment�FilesystemWheel�MemoryWheel�Wheel) r r r r r �get_default_environment�get_environment�get_wheel_distribution�select_backend�returnc �^ � t j dk rdS 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_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� ValueError�boolr �os�environ�importlib.metadata�getattr�metadata�� importlibs �/builddir/build/BUILD/imunify360-venv-2.5.3/opt/imunify360/venv/lib/python3.11/site-packages/pip/_internal/metadata/__init__.py�_should_use_importlib_metadatar+ s� � �"