g *ddlZddlZddlZddlZddlmZmZddlmZddl m Z ddej j dej j dej j gZe rddhZd ejeeDZdd eeed efd Zd efd Zd efdZdS)N)ListOptional)main)WINDOWSpip.z.exec8g|]}d|S)r )join).0partss ]/var/www/html/mpstechhub/venv/lib/python3.11/site-packages/pip/_internal/utils/entrypoints.py rs2  argsreturnc^tjdt|S)aCentral 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. aWARNING: 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)rs r_wrapperrs1J " ::rctrdnd}tjtj|}tjtjdd tj }tj||v}|rtD]{}tj |}tj||}|rCtj|r$tj||r|cS|t!dS)zHTry to figure out the best way to invoke pip in the current environment.ScriptsbinPATHr z -m pip)rospathr rprefixnormcaseenvirongetsplitpathsep_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_pipr1.s$+6yyGLL-=>>M!!"*.."<"<==CCBJOOJg&&}55CO  ) H%|H55  " ]H E E   GNN#455 G$$$%  233 < < <rBsY !!!!!!!!''''''...... "#  "";#  ;;3#3#9;;  v,&Y&'8:MNN 8DI&#.=#====6 S      r