+ j7 aR4t<0t^RIt^RIt^RIt^RIt^RIt^RIt^RIHtH t H t ^RI H t H t ^RIHt^RIHt^RIHt^RIHt^RIHtHtHtHtHtHt.R5Ot]P<!]4t ]!!]R R 4t"]^k]PFR68t$R R lt%]%!4t&]&'g^R IH't']$'d]&'g]PPt)M ]PTt)RRlt+RRlt,]PZ!RR7RRl4t.]PZ!RR7RRl4t/]PZ!RR7RRl4t0]PZ!RR7RRl4t1]PZ!RR7RRl4t2]PZ!RR7RRl4t3RR lt4]PZ!RR7R!R"R#RR$RR%R/R&R'll4t5R7R(R)llt6R*R+lt7R,R-lt8R.R/lt9R0R1lt:R2R3lt;R#)8N)AnyDictOptional) SCHEME_KEYSScheme)WINDOWS) deprecated)running_under_virtualenv) _sysconfig)USER_CACHE_DIRget_major_minor_versionget_src_prefixis_osx_framework site_packages user_site platlibdirlibc$V^8dQhR\/#returnbool)formats"_/home/ralf/ical-fahrzeuge/venv/lib/python3.14/site-packages/pip/_internal/locations/__init__.py __annotate__r.s R Rt Rc>\\\R\44#)a\This 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_DEFAULTrr_should_use_sysconfigr$.s  #79OP QQr _distutilsc$V^8dQhR\/#rr)rs"rrrLs , ,t ,rc^^RIHpVR,R,pVR8H# \dR#i;i)zkThe resolution to bpo-44860 will change this incorrect platlib. See . INSTALL_SCHEMES unix_userplatlibFz $usersite)distutils.command.installr*KeyError)r*unix_user_platlibs r_looks_like_bpo_44860r0Ls= :+K8C  ++ s  ,,cRV^8dQhR\\\3,R\/#)rschemer)rstrr)rs"rrrZs&JJS#XJ4JrcVR,pRV9dVPRR\ R24pRV9dR#VPRR4pVPRR4VR,8H#) r,z /$platlibdir///lib64/Fz/lib/z $platbase/z$base/purelib)replace _PLATLIBDIR)r2r, unpatcheds& r+_looks_like_red_hat_patched_platlib_purelibr;ZseYG'!///Q{m13EF 73I   \8 4y8I IIr)maxsizec$V^8dQhR\/#rr)rs"rrres   rca^RIHo\;QJdV3RlR4F 'dK R# R#!V3RlR44#)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. r)c3b<"TF$pVS9;'d\SV,4xK& R#5iN)r;).0kr*s& r *_looks_like_red_hat_lib..ls>.A _ L L 78J K L-s//FT) unix_prefix unix_home)r-r*allr)s@r_looks_like_red_hat_librHdsG : 3.3333. rc$V^8dQhR\/#rr)rs"rrrtsOO4Orc2^RIHpRV9;'dRV9#)z#Debian adds two additional schemes.r) deb_system unix_local)r-r*r)s r_looks_like_debian_schemerMss: ? * N N|/NNrc$V^8dQhR\/#rr)rs"rrr|sDrcX^RIHp^RIHpV!V!44pVP 4VP \ PP\P 4 R28H;'d>VP\ PP\P4 R28H#)aHRed 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. )install) Distributionz/local) r-rPdistutils.distrQfinalize_options exec_prefixospathnormpathsysprefix)rPrQcmds r_looks_like_red_hat_schemer[{s2+|~&C bgg..s?@GG B B JJRWW--cjj9:&A Arc$V^8dQhR\/#rr)rs"rrrs H Hd Hrc\fR#\P!RRR7pRTR,9;'d R\9# \dR#i;i)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. F posix_user)r2expandr6r7)rr! get_pathsr.pathss r_looks_like_slackware_schemercsW##<F i( ( G GYi-GG sA AAc$V^8dQhR\/#rr)rs"rrrsrca\P!RRR7o\;QJd&RV3RlR44F 'dK R# R#!RV3RlR444#)aqMSYS2 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)r_c3"TF5pRV9;'d$RV9;'dVPR4'*xK7 R#5i)Librz site-packagesN)endswith)rAps& rrC1_looks_like_msys2_mingw_scheme..s>?A QII5A:IIajj.I*II?s ? ??c36<"TFpSV,xK R#5ir@r#)rAkeyrbs& rrCrks?(>%**(>sTr,r7)r!r`rGras@r_looks_like_msys2_mingw_schemeros^   U 3E 3?(>?3333?(>? rchV^8dQhR\PR\PR\RR/#)roldnewrmrN)pathlibPathr3)rs"rrrs6CC',,CW\\C3C4CrcFRpRp\P\WBW0V4R#)z(https://github.com/pypa/pip/issues/10151zSValue for %s does not match. Please report this to <%s> distutils: %s sysconfig: %sN)loggerlog_MISMATCH_LEVEL)rqrrrm issue_urlmessages&&$ r_warn_mismatchedr{s%:I   JJicBrcpV^8dQhR\PR\PR\R\/#)rrqrrrmr)rsrtr3r)rs"rrrs07<<gllCDrc0W8XdR#\WVR7R#)FrmT)r{)rqrrrms&&$r_warn_if_mismatchrs zS3' ruserFhomerootrYc V^8dQhR\R\\,R\\,R\\,RR/#)rrrrrYrN)rrr3)rs"rrrsOLL L 3-L 3- L SM L  Lrcd.ROp\P\RPV4WW#4R#)Additional context: N)rz user = %rz home = %rz root = %rz prefix = %r)rvrwrxjoin)rrrrYpartss$$$$ r _log_contextrs& E JJ % 0$dKrcV^8dQhR\R\R\\,R\\,R\R\\,R\/#)r dist_namerrrisolatedrYr)r3rrr)rs"rrrscccc c 3-c 3- c  c SM c crc 8 aa\P!VVVVVVR7p\'dV#\P!VVVVVVR7o.p\EFp\ P !\SV44p \ P !\Wh44p W8XdKK\PPR8H;'dyVRJ;'dmVR9;'d`V PV P8H;'d?V PPR4;'dV PPR4p V 'dKT;'dp\4;'d^VR8H;'dQV PPV P8H;'d&V PPPR4p V 'dEKvVR8Xd\4'dEKT;'d<VR8H;'d/\'*;'d\ R8g;'d \#4p V 'dEKT;'d+VR9;'d\'*;'d \%4pV'dEKT;'gT;'gT;'g \'4'*;'dV P(R,R8H;'d\+V P(4^8;'dyV P(^,R8H;'d[\+V P(4^8;'gV P(^,R 8g;'d\-4;'g \/4pV'dEK\;'dVR9;'d \14pV'dEKE\2P4!R R 7;'d\'*;'dVR9pV'dEKVP7WR V 234EK V'gS#\P8!VVVVVVR R 7o\:;QJd$VV3Rl\4F 'gK R M RM!VV3Rl\44'd\=RRRR7S#VFwrp\?WVR7K \AWW5R7S#))rrrrrYpypyNr,pythonheadersr:NusrlocalT) check_homezscheme.)ignore_config_filesc3P<"TFpSV,\SV48gxK R#5ir@)r )rArB default_oldrqs& rrCget_scheme..gs Bk;q>WS!_ ,ks#&FzConfiguring 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_inr~)rrrrYrn)rr)rinclude platinclude)!r get_scheme_USE_SYSCONFIGr&rrsrtr rXimplementationnameparent startswithrrHrr9r0rcr rlenr[rMror!is_python_buildappenddistutils_schemeanyr r{r)rrrrrrYrrwarning_contextsrBold_vnew_vskip_pypy_special_case$skip_osx_framework_user_special_caseskip_bpo_44860skip_slackware_user_schemeskip_linux_system_special_caseskip_msys2_mingw_bugskip_cpython_buildrmrrqs&&&&&& @@rrrsb        C~        C [ WS!_- WS_- >     # #v - . .D  . .++ . .  , . . %%h/  . .  %%f-  "   7 7 " 7 7Y 7 7 ##u||3 7 7 !!,,X6 - 0  >577   ( (Y ( (  ( (u$ ( (&'     / /++ / /  / /-. # &  EEEEEE+C+E F N N C $44 N NEKK 1$ N N A%' N NU[[!A%BBQ7)B  N N ,-LL1J1L ' *   X X33 X X8V8X    % % 6 ; ;  ; ;::   } =>GJ  --    K s Bk Bsss Bk BBBL   .c3/.dD@ Jrc$V^8dQhR\/#rr3)rs"rrr|src\P!4p\'dV#\P!4p\ \ P !V4\ P !V4RR7'd \4V#) bin_prefixr~)r get_bin_prefixrr&rrsrtrrrrqs rrr|sS  # # %C~  # # %Cc*GLL,=<PP Jrc$V^8dQhR\/#rr)rs"rrrs88c8rcF\P!RRR7P#)T)r)r rscriptsr#rr get_bin_userrs  $ / 7 77rc0V^8dQhR\R\/#)rvaluer)r3r)rs"rrrsrc<\4'gR#VR8XdR#R#)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)rM)rs&r$_looks_like_deb_system_dist_packagesrs % & & 00 rc$V^8dQhR\/#rr)rs"rrrs  S rc(\P!4p\'dV#\P!4p\ V4'dV#\ \ P!V4\ P!V4RR7'd \4V#)z,Return the default pure-Python lib location.r7r~) r get_purelibrr&rrrsrtrrs rrrsc  "C~  "C+C00 c*GLL,=9MM Jrc$V^8dQhR\/#rr)rs"rrrs  S rc,\P!4p\'dV#^RIHpVP!4p\ V4'dV#\ \P!V4\P!V4RR7'd \4V#)z0Return the default platform-shared lib location.r%r,r~) r get_platlibrrr&rrrsrtr)rrr&rqs rrrsf  "C~   "C+C00 c*GLL,=9MM Jrc@V^8dQh/^\9d \;R&#)rr9)__conditional_annotations__r3)rs"rrrsP54S4Qr) r rrr rrrrrr)r )FNNFN)=r functoolsloggingrUrsrXr!typingrrrpip._internal.models.schemerrpip._internal.utils.compatrpip._internal.utils.deprecationr pip._internal.utils.virtualenvr rr baser r rrrr__all__ getLogger__name__rvr r9 version_infor"r$rr&WARNINGrxDEBUGr0r; lru_cacherHrMr[rcror{rrrrrrrrr)rs@rrs  &&;.6C    8 $3 e4 4))W4 R'(.ooOmmO ,J T" #  T"O#O T"#& T" H# H T"#" T"C#C T"LLL L ! L#L$cL8"  r