U >hM: @sUddlZddlZddlZddlZddlZddlZddlmZmZm Z m Z m Z ddl m Z mZddlmZddlmZddlmZddlmZdd lmZmZmZmZmZmZd d d d ddddddg Zee Z!e"eddZ#e$e%d<ej&dkZ'e(dddZ)e)Z*e*sddlm+Z+e'r(e*s(ej,Z-nej.Z-e(dddZ/ee$e$fe(ddd Z0ej1dd!e(dd"d#Z2ej1dd!e(dd$d%Z3ej1dd!e(dd&d'Z4ej1dd!e(dd(d)Z5ej1dd!e(dd*d+Z6e e$e e$ddfd,d-d.Z7ej1dd!ej8ej8e$dd/d0d1Z9ej8ej8e$e(d/d2d3Z:ej1dd!d4dddd5e(e e$e e$e e$dd6d7d8Z;dBe$e(e e$e e$e(e e$ed9d:dZe$e(d=d>d?Z?e$dd@dZ@e$ddAdZAdS)CN)AnyDict GeneratorOptionalTuple) SCHEME_KEYSScheme)WINDOWS) deprecated)running_under_virtualenv) _sysconfig)USER_CACHE_DIRget_major_minor_versionget_src_prefixis_osx_framework site_packages user_siterget_bin_prefix get_bin_userr get_platlib get_purelib get_schemerrrZ platlibdirlib _PLATLIBDIR) )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)boolgetattr sysconfig_USE_SYSCONFIG_DEFAULTr"r"D/tmp/pip-unpacked-wheel-zvxvnq2j/pip/_internal/locations/__init__.py_should_use_sysconfig.s r$ _distutilscCs<ddlm}z|dd}Wntk r2YdSX|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_44860Ls  r-)schemercCsP|d}d|kr$|ddtd}d|kr0dS|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_purelibZs r3)maxsizecs"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"|]}|kot|VqdSN)r3.0kr'r"r# lsz*_looks_like_red_hat_lib..) unix_prefix unix_home)r+r(allr"r"r'r#_looks_like_red_hat_libds  r=cCsddlm}d|kod|kS)z#Debian adds two additional schemes.rr' deb_system unix_local)r+r(r'r"r"r#_looks_like_debian_schemess 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   rLcCsJtdkr dSztjddd}Wntk r4YdSXd|dkoHdtkS)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_schemesrRcs.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|ko d|ko |d VqdS)Librz site-packagesN)endswith)r7pr"r"r#r9sz1_looks_like_msys2_mingw_scheme..c3s|]}|VqdSr5r")r7keyrPr"r#r9sr*r1)r rOr<r"r"rPr#_looks_like_msys2_mingw_schemes rY)partsrccshtd}ttdd}|r(|r(||s6|EdHdS|D](}||r\|ddt|}|Vq:dS)N LDVERSIONabiflagsr)r get_config_varrrIrUlen)rZZ ldversionr\partr"r"r# _fix_abiflagss    r`)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)rarbrWZ issue_urlmessager"r"r#_warn_mismatchedsrgcCs||kr dSt|||ddS)NFrWT)rg)rarbrWr"r"r#_warn_if_mismatchsriFuserhomerootrJ)rkrlrmrJrcCs,dddddg}ttd|||||dS)NzAdditional context:z user = %rz home = %rz root = %rz prefix = %r )rcrdrejoin)rkrlrmrJrZr"r"r# _log_contexts rp) dist_namerkrlrmisolatedrJrc 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_inrhrj)"r r_USE_SYSCONFIGr&rpathlibPathrrIimplementationnameparent startswithrr=r version_inforr-rRr rZr^rLr@rYr is_python_buildappenddistutils_schemeanyr rgrp)rqrkrlrmrrrJrbZwarning_contextsr8Zold_vZnew_vZskip_pypy_special_caseZ$skip_osx_framework_user_special_caseZskip_bpo_44860Zskip_slackware_user_schemeZskip_linux_system_special_caseZskip_msys2_mingw_bugZskip_cpython_buildrWr"r}r#rs             cCs<t}tr|St}tt|t|ddr8t|S)NZ bin_prefixrh)r rrr&rirrrprbrar"r"r#rscCstjdddjS)NT)rk)r rscriptsr"r"r"r#rs)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.r1rh) r rrr&rrirrrprr"r"r#rscCsTt}tr|Sddlm}|}t|r0|Stt|t|ddrPt |S)z0Return the default platform-shared lib location.r r%r*rh) r rrrr&rrirrrp)rbr&rar"r"r#rs )FNNFN)B functoolsloggingrFrrIr typingrrrrrpip._internal.models.schemerrpip._internal.utils.compatr pip._internal.utils.deprecationr pip._internal.utils.virtualenvr rr baserrrrrr__all__ getLogger__name__rcrrstr__annotations__rr!rr$rr&WARNINGreDEBUGr-r3 lru_cacher=r@rLrRrYr`rrgrirprrrrrrr"r"r"r#s                  (