a ijM7 @sLUddlmZddlZddlZddlZddlZddlZddlZddlm Z m Z ddl m Z ddl mZddlmZddlmZdd lmZmZmZmZmZmZgd ZeeZeed d Zd e d<ej!dkZ"ddddZ#e#Z$e$sddlm%Z%e"re$sej&Z'nej(Z'ddddZ)dddddZ*ej+ddddZ,ej+ddddZ-ej+dddd Z.ej+ddd!d"Z/ej+ddd#d$Z0ej+d%d%d d&d'd(d)Z1d%d%d dd'd*d+Z2ej+d,dddd-dd.d.d.d&d/d0d1Z3dAd dd.d.dd.d2d3d4d5Z4d dd6d7Z5d dd8d9Z6d dd:d;d<Z7d dd=d>Z8d dd?d@Z9dS)B) annotationsN) SCHEME_KEYSScheme)WINDOWS) deprecated)running_under_virtualenv) _sysconfig)USER_CACHE_DIRget_major_minor_versionget_src_prefixis_osx_framework site_packages user_site) r get_bin_prefix get_bin_userr get_platlib get_purelib get_schemer rr platlibdirlibstr _PLATLIBDIR) bool)returncCstttdtS)axThis function determines the value of _USE_SYSCONFIG. By default, pip uses sysconfig on Python 3.10+. But Python distributors can override this decision by setting: sysconfig._PIP_USE_SYSCONFIG = True / False Rationale in https://github.com/pypa/pip/issues/10647 This is a function for testability, but should be constant during any one run. _PIP_USE_SYSCONFIG)rgetattr sysconfig_USE_SYSCONFIG_DEFAULTr!r!^/home/ghrups/robot-bench/.venv/lib/python3.9/site-packages/pip/_internal/locations/__init__.py_should_use_sysconfig/s r# _distutilscCs:ddlm}z|dd}Wnty0YdS0|dkS)zsThe resolution to bpo-44860 will change this incorrect platlib. See . rINSTALL_SCHEMES unix_userplatlibFz $usersite)distutils.command.installr'KeyError)r'unix_user_platlibr!r!r"_looks_like_bpo_44860Ms   r-zdict[str, str])schemercCsP|d}d|vr$|ddtd}d|vr0dS|dd}|dd|d kS) Nr)z /$platlibdir///lib64/Fz/lib/z $platbase/z$base/purelib)replacer)r.r) unpatchedr!r!r"+_looks_like_red_hat_patched_platlib_purelib[s r4cs"ddlmtfdddDS)zRed Hat patches platlib in unix_prefix and unix_home, but not purelib. This is the only way I can see to tell a Red Hat-patched Python. rr&c3s"|]}|vot|VqdSN)r4.0kr&r!r" msz*_looks_like_red_hat_lib..) unix_prefix unix_home)r*r'allr!r!r&r"_looks_like_red_hat_libes  r=cCsddlm}d|vod|vS)z#Debian adds two additional schemes.rr& deb_system unix_local)r*r'r&r!r!r"_looks_like_debian_schemets r@cCs^ddlm}ddlm}||}||jtjt jdko\|j tjt j dkS)a\Red Hat patches ``sys.prefix`` and ``sys.exec_prefix``. Red Hat's ``00251-change-user-install-location.patch`` changes the install command's ``prefix`` and ``exec_prefix`` to append ``"/local"``. This is (fortunately?) done quite unconditionally, so we create a default command object without any configuration to detect this. r)install) Distributionz/local) r*rAdistutils.distrBfinalize_options exec_prefixospathnormpathsysprefix)rArBcmdr!r!r"_looks_like_red_hat_scheme|s   rLcCsHtdur dSztjddd}Wnty2YdS0d|dvoFdtvS)zSlackware patches sysconfig but fails to patch distutils and site. Slackware changes sysconfig's user scheme to use ``"lib64"`` for the lib path, but does not do the same to the site module. NF posix_user)r.expandr0r1)rr get_pathsr+pathsr!r!r"_looks_like_slackware_schemes rRcs.tjdddtddfdddDDS)aMSYS2 patches distutils and sysconfig to use a UNIX-like scheme. However, MSYS2 incorrectly patches sysconfig ``nt`` scheme. The fix is likely going to be included in their 3.10 release, so we ignore the warning. See msys2/MINGW-packages#9319. MSYS2 MINGW's patch uses lowercase ``"lib"`` instead of the usual uppercase, and is missing the final ``"site-packages"``. ntF)rNcss*|]"}d|vo d|vo |d VqdS)Librz site-packagesN)endswith)r7pr!r!r"r9sz1_looks_like_msys2_mingw_scheme..c3s|]}|VqdSr5r!)r7keyrPr!r"r9r)r1)rrOr<r!r!rPr"_looks_like_msys2_mingw_schemes rZz pathlib.PathNone)oldnewrWrcCs d}d}tt|||||dS)Nz(https://github.com/pypa/pip/issues/10151zSValue for %s does not match. Please report this to <%s> distutils: %s sysconfig: %s)loggerlog_MISMATCH_LEVEL)r\r]rW issue_urlmessager!r!r"_warn_mismatchedsrccCs||kr dSt|||ddS)NFrWT)rc)r\r]rWr!r!r"_warn_if_mismatchsreFuserhomerootrJz str | None)rgrhrirJrcCs&gd}ttd|||||dS)N)zAdditional context:z user = %rz home = %rz root = %rz prefix = %r )r^r_r`join)rgrhrirJpartsr!r!r" _log_contextsrmr) dist_namergrhriisolatedrJrc stj||||||d}tr|Stj||||||dg}tD]}tt|} tt||} | | krlq.zConfiguring installation scheme with distutils config files is deprecated and will no longer work in the near future. If you are using a Homebrew or Linuxbrew Python, please see discussion at https://github.com/Homebrew/homebrew-core/issues/76621)reason replacementgone_inrdrf)!r r_USE_SYSCONFIGr%rpathlibPathrrIimplementationnameparent startswithr r=rrr-rRrrllenrLr@rZris_python_buildappenddistutils_schemeanyrrcrm)rnrgrhrirorJr]warning_contextsr8old_vnew_vskip_pypy_special_case$skip_osx_framework_user_special_caseskip_bpo_44860Zskip_slackware_user_schemeskip_linux_system_special_caseskip_msys2_mingw_bugskip_cpython_buildrWr!rzr"rs             rcCs<t}tr|St}tt|t|ddr8t|S)N bin_prefixrd)r rrr%rerrrmr]r\r!r!r"r}srcCstjdddjS)NT)rg)r rscriptsr!r!r!r"rsr)valuercCsts dS|dkrdSdS)aCheck if the value is Debian's APT-controlled dist-packages. Debian's ``distutils.sysconfig.get_python_lib()`` implementation returns the default package path controlled by APT, but does not patch ``sysconfig`` to do the same. This is similar to the bug worked around in ``get_scheme()``, but here the default is ``deb_system`` instead of ``unix_local``. Ultimately we can't do anything about this Debian bug, and this detection allows us to skip the warning when needed. Fz/usr/lib/python3/dist-packagesT)r@)rr!r!r"$_looks_like_deb_system_dist_packagess rcCsHt}tr|St}t|r$|Stt|t|ddrDt|S)z,Return the default pure-Python lib location.r1rd) r rrr%rrerrrmrr!r!r"rsrcCsTt}tr|Sddlm}|}t|r0|Stt|t|ddrPt |S)z0Return the default platform-shared lib location.rr$r)rd) r rrrr%rrerrrm)r]r%r\r!r!r"rs r)FNNFN): __future__r functoolsloggingrFrrIrpip._internal.models.schemerrpip._internal.utils.compatrpip._internal.utils.deprecationrpip._internal.utils.virtualenvrrr baser r r r rr__all__ getLogger__name__r^rr__annotations__ version_infor r#rr%WARNINGr`DEBUGr-r4cacher=r@rLrRrZrcrermrrrrrrr!r!r!r"sp           '