*,h ddlZddlZddlZddlZddlmZmZddlmZddl m Z ddejjdejjdejjgZe r4ddhZej eeDcgc]}dj#|c}Zdd eeed efd Zd efd Zd efd Zycc}w)N)ListOptional)main)WINDOWSpip.z.exeargsreturncVtjjdt|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)r s a/var/www/html/Resume-Scraper/venv/lib/python3.12/site-packages/pip/_internal/utils/entrypoints.py_wrapperrs'JJ " :ctrdnd}tjjtj |}tjj tjjddjtj}tjj ||v}|rtD]~}tj|}tjj||}|s;tjj|s[tjj||s||cSt!dS)zHTry to figure out the best way to invoke pip in the current environment.ScriptsbinPATHr z -m pip)rospathjoinr 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%||H5  " ]H E  GGNN#45GG$$$%   23 4G <r>s !'.  #   !" #   !3#3#3#9#9":;  v,'Y&&'8:MN   8DI&#.=#=6 S qs C