File manager - Edit - /opt/saltstack/salt/lib/python3.10/site-packages/pip/_internal/utils/__pycache__/entrypoints.cpython-310.pyc
Back
o ;j� � @ s� d dl mZ d dlZd dlZd dlZd dlZd dlmZ d dlm Z ddej j� �dej j� dej j� �gZ e rGddhZd d � e�e e�D �Z dddd�Zddd�Zddd�ZdS )� )�annotationsN)�main)�WINDOWSZpip�.� z.exec C s g | ]}d � |��qS )r )�join)�.0�parts� r �S/opt/saltstack/salt/lib/python3.10/site-packages/pip/_internal/utils/entrypoints.py� <listcomp> s ��r �args�list[str] | None�return�intc C s t j�d� t| �S )a� Central wrapper for all old entrypoints. Historically pip has had several entrypoints defined. Because of issues arising from PATH, sys.path, multiple Pythons, their interactions, and most of them having a pip installed, users suffer every time an entrypoint gets moved. To alleviate this pain, and provide a mechanism for warning users and directing them to an appropriate place for help, we now define all of our old entrypoints as wrappers for the current one. a WARNING: pip is being invoked by an old script wrapper. This will fail in a future version of pip. Please see https://github.com/pypa/pip/issues/5599 for advice on fixing the underlying issue. To avoid this problem you can invoke Python with '-m pip' instead of running pip directly. )�sys�stderr�writer )r r r r �_wrapper s �r �strc C s� t rdnd} tj�tj| �}tj�tj�dd��� tj �}tj�|�|v }|rKtD ]!}t� |�}tj�||�}|rJtj�|�rJtj�||�rJ| S q)t� � d�S )zHTry to figure out the best way to invoke pip in the current environment.�Scripts�bin�PATHr z -m pip)r �os�pathr r �prefix�normcase�environ�get�split�pathsep�_EXECUTABLE_NAMES�shutil�which�exists�samefile�#get_best_invocation_for_this_python)Zbinary_directoryZ binary_prefix� path_partsZexe_are_in_PATH�exe_name�found_executableZbinary_executabler r r � get_best_invocation_for_this_pip/ s( � ����r* c C sB t j} tj�| �}t�|�}|rtj�t�|�t�| ��r|S | S )z<Try to figure out the best way to invoke the current Python.) r � executabler r �basenamer"