a h,Me<ã @sÎUddlZddlZddlZddlZddlZddlZddlmZmZm Z m Z mZddlm Z mZddlmZddlmZddlmZddlmZdd lmZmZmZmZmZmZgd ¢Ze e ¡Z!e"eddƒZ#e$e%d <ej&dkZ'e(dœdd„Z)e)ƒZ*e*sddlm+Z+e're*sej,Z-nej.Z-e(dœdd„Z/ee$e$fe(dœdd„Z0ej1dde(dœdd„ƒZ2ej1dde(dœdd„ƒZ3ej1dde(dœdd„ƒZ4ej1dde(dœdd „ƒZ5ej1dde(dœd!d"„ƒZ6ee$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$ed0œd1d2„Ze$e(d7œd8d9„Z?e$dœd:d;„Z@e$dœd. r©ÚINSTALL_SCHEMESZ unix_userÚplatlibFz $usersite)Údistutils.command.installr)ÚKeyError)r)Zunix_user_platlibr#r#r$Ú_looks_like_bpo_44860Lsr-)ÚschemercCsP|d}d|vr$| ddt›d¡}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_purelibZsr3)Úmaxsizecs"ddlm‰t‡fdd„dDƒƒS)z‘Red 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ˆ|ƒVqdS©N)r3©Ú.0Úkr(r#r$Ú lsþz*_looks_like_red_hat_lib..)Zunix_prefixZ unix_home)r+r)Úallr#r#r(r$Ú_looks_like_red_hat_libdsýr;cCsddlm}d|vod|vS)z#Debian adds two additional schemes.rr(Z deb_systemZ unix_local)r+r)r(r#r#r$Ú_looks_like_debian_schemessr<cCs^ddlm}ddlm}||ƒƒ}| ¡|jtj t j¡›dko\|j tj t 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=Zdistutils.distr>Zfinalize_optionsÚexec_prefixÚosÚpathÚnormpathÚsysÚprefix)r=r>Úcmdr#r#r$Ú_looks_like_red_hat_scheme{s þrFcCsHtdurdSztjddd}Wnty2YdS0d|dvoFdtvS)zÌSlackware 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_schemesrLcs.tjddd‰tdd„‡fdd„dDƒDƒƒS)a‰MSYS2 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)rHcss*|]"}d|vo d|vo | d¡VqdS)ZLibrz site-packagesN)Úendswith)r7Úpr#r#r$r9«sÿz1_looks_like_msys2_mingw_scheme..c3s|]}ˆ|VqdSr5r#)r7ÚkeyrJr#r$r9ó©r*r1)r!rIr:r#r#rJr$Ú_looks_like_msys2_mingw_schemeŸsþrS)Úpartsrccsht d¡}ttddƒ}|r(|r(| |¡s6|EdHdS|D](}| |¡r\|ddt|ƒ…}|Vq:dS)NZ LDVERSIONÚabiflagsr)r!Úget_config_varr rCrNÚlen)rTZ ldversionrUÚpartr#r#r$Ú _fix_abiflags±s rY)ÚoldÚnewrPrcCs d}d}t t|||||¡dS)Nz(https://github.com/pypa/pip/issues/10151zSValue for %s does not match. Please report this to <%s> distutils: %s sysconfig: %s)ÚloggerÚlogÚ_MISMATCH_LEVEL)rZr[rPZ issue_urlÚmessager#r#r$Ú_warn_mismatchedÁsÿr`cCs||krdSt|||ddS)NF©rPT)r`)rZr[rPr#r#r$Ú_warn_if_mismatchÌsrbF©ÚuserÚhomeÚrootrD)rdrerfrDrcCs&gd¢}t td |¡||||¡dS)N)zAdditional context:z user = %rz home = %rz root = %rzprefix = %rÚ )r\r]r^Újoin)rdrerfrDrTr#r#r$Ú_log_contextÓsri)Ú dist_namerdrerfÚisolatedrDrc sötj||||||d}tr|Stj||||||d‰g}tD]4}t tˆ|ƒ¡} t t||ƒ¡} | | krlq.zöConfiguring 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ÚreplacementÚgone_inrarc)$r rÚ_USE_SYSCONFIGr'rÚpathlibÚPathr rCÚimplementationÚnameÚparentÚ startswithrr;r Úversion_inforr-rLrrTrWrFr<ÚtuplerYrSr!Úis_python_buildÚappendZdistutils_schemeÚanyr r`ri)rjrdrerfrkrDr[Zwarning_contextsr8Zold_vZnew_vZskip_pypy_special_caseZ$skip_osx_framework_user_special_caseZskip_bpo_44860Zskip_slackware_user_schemeZskip_linux_system_special_caseZskip_sysconfig_abiflag_bugZskip_msys2_mingw_bugZskip_cpython_buildrPr#rwr$ræsúú ÿþ ý ü úÿþýûÿþýüúÿþüÿþýüúÿþüÿÿýù ø rcCs<t ¡}tr|St ¡}tt |¡t |¡ddr8tƒ|S)NZ bin_prefixra)r rr{r'rbr|r}ri©r[rZr#r#r$r˜srcCstjdddjS)NÚT)rd)r rÚscriptsr#r#r#r$r£sr)ÚvaluercCstƒs dS|dkrdSdS)aõCheck 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<)rŠr#r#r$Ú$_looks_like_deb_system_dist_packages§s r‹cCsHt ¡}tr|St ¡}t|ƒr$|Stt |¡t |¡ddrDtƒ|S)z,Return the default pure-Python lib location.r1ra) r rr{r'r‹rbr|r}rir‡r#r#r$r¸srcCsTt ¡}tr|Sddlm}| ¡}t|ƒr0|Stt |¡t |¡ddrPt ƒ|S)z0Return the default platform-shared lib location.rr&r*ra) r rr{rˆr'r‹rbr|r}ri)r[r'rZr#r#r$rÆsr)FNNFN)BÚ functoolsÚloggingr@r|rCr!ÚtypingrrrrrZpip._internal.models.schemerrÚpip._internal.utils.compatr Úpip._internal.utils.deprecationr Úpip._internal.utils.virtualenvrrˆr ÚbaserrrrrrÚ__all__Ú getLoggerÚ__name__r\r rÚstrÚ__annotations__r‚r"rr%r{r'ÚWARNINGr^ÚDEBUGr-r3Ú lru_cacher;r<rFrLrSrYr}r`rbrirrrr‹rrr#r#r#r$ÚsŽ ûúúù3