R`iC d dl Z d dlZd dlZd dlZd dlmZmZ d dlmZ d dl m
Z
ddej j dej j dej j gZe
r4ddhZ e j ee D cg c] } dj# | c} Zdd eee d
ed efd Zd efd
Zd efdZyc c} w ) N)ListOptional)main)WINDOWSpip. z.exeargs_nowarnreturnc Z |s t j 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.
)sysstderrwriter )r
r s /builddir/build/BUILDROOT/alt-python312-pip-23.3.1-3.el8.x86_64/opt/alt/python312/lib/python3.12/site-packages/pip/_internal/utils/entrypoints.py_wrapperr s*
&
: c t rdnd} t j j t j
| }t j j
t j j dd j t j }t j j
| |v }|rt D ]~ }t j | }t j j || }|s;t j j | s[t j j || s||c S t! dS )zHTry to figure out the best way to invoke pip in the current environment.ScriptsbinPATHr z -m pip)r ospathjoinr prefixnormcaseenvirongetsplitpathsep_EXECUTABLE_NAMESshutilwhichexistssamefile#get_best_invocation_for_this_python)binary_directory
binary_prefix
path_partsexe_are_in_PATHexe_namefound_executablebinary_executables r get_best_invocation_for_this_pipr. / s $+yGGLL-=>M !!"**.."<=CCBJJOJgg&&}5CO)H %||H 5 " ]H E GGNN#45GG$$$%
* 23
4G <r@ s
! ' .
#
!" #
!3#3#3#9#9":;
v, 'Y&&'8:MNNE N 8DI& 0=# =6 S ss
C