+ Îi ^RIHt^RIt^RIt^RIt^RIt^RIHt^RIH t RR]PP 2R]PP R]PP 2.t ] 'd7RR0t]P!] ]4Uu.uFpRP!V4NK upt RR R lltR R ltR RltR#uupi)) annotationsN)main)WINDOWSpip.z.exec V^8dQhRRRR/#)argszlist[str] | Nonereturnint)formats"n/Users/ahmad/.openclaw/workspace/scripts/.venv/lib/python3.14/site-packages/pip/_internal/utils/entrypoints.py __annotate__rs#scV\PPR4\V4#)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&r_wrapperrs'JJ " :rcV^8dQhRR/#r r strr)rs"rrr/s==#=rc\'dRMRp\PP\P V4p\PP \PPRR44P\P4p\PP V4V9pV'd\Fp\P!V4p\PPW4pV'gKB\PPV4'gKi\PPVV4'gKVu# \!4 R2#)zHTry to figure out the best way to invoke pip in the current environment.ScriptsbinPATHrz -m pip)rospathjoinrprefixnormcaseenvirongetsplitpathsep_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_pipr5/s$+GyGGLL-=>M!!"**.."<=CCBJJOJgg&&}5CO)H%||H5  " ] E   GGNN#455GG$$$%  *23 4G <rGs" '.  #   !" #   !3#3#3#9#9":;  v,&&'8:MNNE N .=6qsC