a 0fM: @sUddlZddlZddlZddlZddlZddlZddlmZmZm Z m Z m Z ddl m Z mZddlmZddlmZddlmZddlmZdd lmZmZmZmZmZmZgd Zee Z!e"ed d Z#e$e%d <ej&dkZ'e(dddZ)e)Z*e*sddlm+Z+e're*sej,Z-nej.Z-e(dddZ/ee$e$fe(dddZ0ej1dde(dddZ2ej1dde(dddZ3ej1dde(dddZ4ej1dde(ddd Z5ej1dde(dd!d"Z6e e$e e$ddfd#d$d%Z7ej1ddej8ej8e$dd&d'd(Z9ej8ej8e$e(d&d)d*Z:ej1ddd+dddd,e(e e$e e$e e$dd-d.d/Z;d>e$e(e e$e e$e(e e$ed0d1d2Ze$e(d7d8d9Z?e$dd:d;Z@e$dd. rINSTALL_SCHEMES unix_userplatlibFz $usersite)distutils.command.installr*KeyError)r*unix_user_platlibr$r$r%_looks_like_bpo_44860Ls   r0)schemercCsP|d}d|vr$|ddtd}d|vr0dS|dd}|dd|d kS) Nr,z /$platlibdir///lib64/Fz/lib/z $platbase/z$base/purelib)replacer)r1r, unpatchedr$r$r%+_looks_like_red_hat_patched_platlib_purelibZs r7)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"|]}|vot|VqdSN)r7.0kr)r$r% lsz*_looks_like_red_hat_lib..) unix_prefix unix_home)r-r*allr$r$r)r%_looks_like_red_hat_libds  rAcCsddlm}d|vod|vS)z#Debian adds two additional schemes.rr) deb_system unix_local)r-r*r)r$r$r%_looks_like_debian_schemess rDcCs^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-rEdistutils.distrFfinalize_options exec_prefixospathnormpathsysprefix)rErFcmdr$r$r%_looks_like_red_hat_scheme{s   rPcCsHtdur 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)r1expandr3r4)rr" get_pathsr.pathsr$r$r%_looks_like_slackware_schemes rVcs.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)rRcss*|]"}d|vo d|vo |d VqdS)Librz site-packagesN)endswith)r;pr$r$r%r=sz1_looks_like_msys2_mingw_scheme..c3s|]}|VqdSr9r$)r;keyrTr$r%r=r,r4)r"rSr@r$r$rTr%_looks_like_msys2_mingw_schemes r^)partsrccshtd}ttdd}|r(|r(||s6|EdHdS|D](}||r\|ddt|}|Vq:dS)N LDVERSIONabiflagsr)r"get_config_varr!rMrYlen)r_ ldversionrapartr$r$r% _fix_abiflagss    rf)oldnewr[rcCs 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)rgrhr[ issue_urlmessager$r$r%_warn_mismatchedsrncCs||kr dSt|||ddS)NFr[T)rn)rgrhr[r$r$r%_warn_if_mismatchsrpFuserhomerootrN)rrrsrtrNrcCs&gd}ttd|||||dS)N)zAdditional context:z user = %rz home = %rz root = %rz prefix = %r )rirjrkjoin)rrrsrtrNr_r$r$r% _log_contextsrw) dist_namerrrsrtisolatedrNrc 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_inrorq)"r r_USE_SYSCONFIGr(rpathlibPathr!rMimplementationnameparent startswithrrAr version_inforr0rVr r_rcrPrDr^r"is_python_buildappenddistutils_schemeanyr rnrw)rxrrrsrtryrNrhwarning_contextsr<old_vnew_vskip_pypy_special_case$skip_osx_framework_user_special_caseskip_bpo_44860skip_slackware_user_schemeskip_linux_system_special_caseskip_msys2_mingw_bugskip_cpython_buildr[r$rr%rs             rcCs<t}tr|St}tt|t|ddr8t|S)N bin_prefixro)r rrr(rprrrwrhrgr$r$r%rsrcCstjdddjS)NT)rr)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)rD)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.r4ro) r rrr(rrprrrwrr$r$r%rsrcCsTt}tr|Sddlm}|}t|r0|Stt|t|ddrPt |S)z0Return the default platform-shared lib location.r r'r,ro) r rrrr(rrprrrw)rhr(rgr$r$r%rs r)FNNFN)B functoolsloggingrJrrMr"typingrrrrrpip._internal.models.schemerrpip._internal.utils.compatr pip._internal.utils.deprecationr pip._internal.utils.virtualenvr rr baserrrrrr__all__ getLogger__name__rir!rstr__annotations__rr#r r&rr(WARNINGrkDEBUGr0r7 lru_cacherArDrPrVr^rfrrnrprwrrrrrrr$r$r$r%s                   (