a s h @sddlmZddlZddlZddlZddlZddlmZddlm Z ddej j dej j dej j gZ e rddhZd d ee eDZ dd d d ddZddddZddddZdS)) annotationsN)main)WINDOWSpip.z.execCsg|]}d|qS)r)join).0partsr [/var/www/html/assistant/venv/lib/python3.9/site-packages/pip/_internal/utils/entrypoints.py sr zlist[str] | Noneint)argsreturncCstjdt|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)rr r r _wrappers rstr)rcCstrdnd}tjtj|}tjtjdd tj }tj||v}|rt D]B}t |}tj||}|rRtj|rRtj||rR|SqRtdS)zHTry to figure out the best way to invoke pip in the current environment.ZScriptsbinPATHrz -m pip)rospathrrprefixnormcaseenvirongetsplitpathsep_EXECUTABLE_NAMESshutilwhichexistssamefile#get_best_invocation_for_this_python)Zbinary_directoryZ binary_prefix path_partsZexe_are_in_PATHexe_namefound_executableZbinary_executabler r r get_best_invocation_for_this_pip/s&    r)cCsBtj}tj|}t|}|r>tjt|t|r>|S|S)zs$