a baii7 @sXUddlmZddlZddlZddlZddlZddlZddlZddlm Z ddl m Z m Z ddl mZddlmZddlmZdd lmZdd lmZmZmZmZmZmZgd ZeeZe ed d Z!de"d<ej#dkZ$ddddZ%e%Z&e&sddlm'Z'e$re&sej(Z)nej*Z)ddddZ+dddddZ,ej-ddddZ.ej-ddddZ/ej-ddd d!Z0ej-ddd"d#Z1ej-ddd$d%Z2ej-d&d&dd'd(d)d*Z3d&d&ddd(d+d,Z4ej-d-dddd.dd/d/d/d'd0d1d2Z5dBddd/d/dd/d3d4d5d6Z6ddd7d8Z7ddd9d:Z8ddd;dd?Z:ddd@dAZ;dS)C) annotationsN)Any) 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. Z_PIP_USE_SYSCONFIG)rgetattr sysconfig_USE_SYSCONFIG_DEFAULTr!r!Z/var/www/html/SiteWeb/venv/lib/python3.9/site-packages/pip/_internal/locations/__init__.py_should_use_sysconfig0s 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'Zunix_user_platlibr!r!r"_looks_like_bpo_44860Ns   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)Z unpatchedr!r!r"+_looks_like_red_hat_patched_platlib_purelib\s r2cs"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)r2.0kr&r!r" nsz*_looks_like_red_hat_lib..) unix_prefix unix_home)r*r'allr!r!r&r"_looks_like_red_hat_libfs  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_schemeus 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*r?distutils.distr@finalize_options exec_prefixospathnormpathsysprefix)r?r@cmdr!r!r"_looks_like_red_hat_scheme}s   rJcCsHtdur 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-expandr/r0)rr get_pathsr+pathsr!r!r"_looks_like_slackware_schemes rPcs.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)rLcss*|]"}d|vo d|vo |d VqdS)Librz site-packagesN)endswith)r5pr!r!r"r7sz1_looks_like_msys2_mingw_scheme..c3s|]}|VqdSr3r!)r5keyrNr!r"r7r)r0)rrMr:r!r!rNr"_looks_like_msys2_mingw_schemes rXz pathlib.PathNone)oldnewrUrcCs 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)rZr[rUZ issue_urlmessager!r!r"_warn_mismatchedsr`cCs||kr dSt|||ddS)NFrUT)r`)rZr[rUr!r!r"_warn_if_mismatchsrbFuserhomerootrHz str | None)rdrerfrHrcCs&gd}ttd|||||dS)N)zAdditional context:z user = %rz home = %rz root = %rz prefix = %r )r\r]r^join)rdrerfrHpartsr!r!r" _log_contextsrjr) dist_namerdrerfisolatedrHrc 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_inrarc)!r r_USE_SYSCONFIGr%rpathlibPathrrGimplementationnameparent startswithrr;rrr,rPrrilenrJr>rXris_python_buildappenddistutils_schemeanyrr`rj)rkrdrerfrlrHr[Zwarning_contextsr6Zold_vZnew_vZskip_pypy_special_caseZ$skip_osx_framework_user_special_caseZskip_bpo_44860Zskip_slackware_user_schemeZskip_linux_system_special_caseZskip_msys2_mingw_bugZskip_cpython_buildrUr!rvr"rs             rcCs<t}tr|St}tt|t|ddr8t|S)NZ bin_prefixra)r rrzr%rbr{r|rjr[rZr!r!r"r~srcCstjdddjS)NT)rd)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.r0ra) r rrzr%rrbr{r|rjrr!r!r"rsrcCsTt}tr|Sddlm}|}t|r0|Stt|t|ddrPt |S)z0Return the default platform-shared lib location.r r$r)ra) r rrzrr%rrbr{r|rj)r[r%rZr!r!r"rs r)FNNFN)< __future__r functoolsloggingrDr{rGrtypingrpip._internal.models.schemerrpip._internal.utils.compatrpip._internal.utils.deprecationrpip._internal.utils.virtualenvrrr baser r r rrr__all__ getLogger__name__r\rr__annotations__ version_infor r#rzr%WARNINGr^DEBUGr,r2cacher;r>rJrPrXr`rbrjrrrrrrr!r!r!r"sr            '