Файловый менеджер - Редактировать - /home/digitalm/venv/lib/python3.7/site-packages/pip/_internal/utils/__pycache__/entrypoints.cpython-37.pyc
Назад
B �5�g� � @ s� d dl Z d dlZd dlZd dlZd dlmZmZ d dlmZ d dl m Z ddejj� �dejj� dejj � �gZe r�ddhZd d � e �ee�D �Zdeee ed�dd �Zed�dd�Zed�dd�ZdS )� N)�List�Optional)�main)�WINDOWS�pip�.� z.exec C s g | ]}d � |��qS )r )�join)�.0�parts� r �@/tmp/pip-install-251nq386/pip/pip/_internal/utils/entrypoints.py� <listcomp> s r )�args�returnc 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 )r c C s� t rdnd} tj�tj| �}tj�tj�dd��� tj �}tj�|�|k}|r�xFtD ]>}t� |�}tj�||�}|rTtj�|�rTtj�||�rT|S qTW 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 s6 t j} tj�| �}t�|�}|r2tj�|| �r2|S | S )z<Try to figure out the best way to invoke the current Python.)r � executabler r �basenamer! r"