2biC S SK r S SKrS SKrS SKrS SKJrJr S SKJr S SK J
r
SS\R R 3S\R R S\R R 3/r\
( a7 SS1r\ R " \\5 V s/ s H n SR# U 5 PM sn rSS \\\ S
\S \4S jjrS \4S
jrS \4S jrgs sn f ) N)ListOptional)main)WINDOWSpip. z.exeargs_nowarnreturnc d U( d [ R R S5 [ U 5 $ )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-python313-pip-23.3.1-3.el8.x86_64/opt/alt/python313/lib/python3.13/site-packages/pip/_internal/utils/entrypoints.py_wrapperr s*
&
: c [ ( a SOSn [ R R [ R
U 5 n[ R R
[ R R SS5 5 R [ R 5 n[ R R
U5 U; nU( a [ H n[ R " U5 n[ R R X5 nU( d MA [ R R U5 ( d Mg [ R R UU5 ( d M Us $ [! 5 S3$ )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 $+GyGGLL-=>M !!"**.."<=CCBJJOJgg&&}5CO)H %||H 5 " ] E GGNN#455GG$$$%
* 23
4G <r@ s
! ' .
#
!" #
!3#3#3#9#9":;
v, &&'8:MNNE N 8DI& 0=# =6 S ss C