LwjtSrSSKJr SSKrSSKrSSKrSSKrSSKrSSKrSSK J r J r J r SSK Jr SSKJr SSKJr SSKJrJr SS KJr SS KJr SS KJr SS KJrJrJrJ r J!r! S SK"J#r#J$r$J%r%J&r&J'r'J(r( S SK%J)r) S SK*J+r+J,r, S SK-J.r. S SK/J0r0 S SK1J2r2J3r3 SSK4J4r5 SSK6J6r7 SSK8J8r9 SSK:J:r; SSKJ>r? \(a SSK@JArA S SKBJCrC \ "S\)S9rD\R"\F5rG"SS \5rHS!rIS"rJ"S#S$\#5rK"S%S&\5rL"S'S(5rM"S)S*\M5rN"S+S,5rOS@S-jrPSAS.jrQSBS/jrRS0rSSCS1jrTSCS2jrUSDS3jrVSES4jrWSFS5jrXSGS6jrYSHS7jrZSIS8jr[SJS9jr\"S:S;\(R5r^SS?\'R5rbg)La Create a wheel that, when installed, will make the source package 'editable' (add it to the interpreter's path, including metadata) per PEP 660. Replaces 'setup.py develop'. .. note:: One of the mechanisms briefly mentioned in PEP 660 to implement editable installs is to create a separated directory inside ``build`` and use a .pth file to point to that directory. In the context of this file such directory is referred as *auxiliary build directory* or ``auxiliary_dir``. ) annotationsN)IterableIteratorMapping)suppress)Enum)cleandoc)chainstarmap)Path)TemporaryDirectory) TracebackType) TYPE_CHECKINGClassVarProtocolTypeVarcast)Command_normalization_path_shutilerrors namespaces)StrPath)py310py312)find_package_path) Distribution)InformationOnlySetuptoolsDeprecationWarning)build)build_py) dist_info)egg_info)install)install_scripts)Self WheelFile_P)boundc8\rSrSrSrSrSrSr\S Sj5r Sr g) _EditableMode5z Possible editable installation modes: `lenient` (new files automatically added to the package - DEFAULT); `strict` (requires a new installation when files are added/removed); or `compat` (attempts to emulate `python setup.py develop` - DEPRECATED). strictlenientcompatcU(d[R$UR5nU[R;a[R "SU<S35eUS:Xa[ R"SSSS9 [U$)NzInvalid editable mode: z. Try: 'strict'.COMPATzCompat editable installsa  The 'compat' editable mode is transitional and will be removed in future versions of `setuptools`. Please adapt your code accordingly to use either the 'strict' or the 'lenient' modes. zuserguide/development_mode.html)see_docs)r/LENIENTupper __members__r OptionErrorr!emit)clsmode_modes گC:\Users\johnn\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.13_qbz5n2kfra8p0\LocalCache\local-packages\Python313\site-packages\setuptools/command/editable_wheel.pyconvert_EditableMode.convertAsv (( (   11 1$$'>thFV%WX X H  ( - -* ;  U##N)r= str | Nonereturnr/) __name__ __module__ __qualname____firstlineno____doc__STRICTr7r5 classmethodr@__static_attributes__rCrBr?r/r/5s*FG F$$rBr/zU New or renamed files may not be automatically picked up without a new installation. zt Options like `package-data`, `include/exclude-package-data` or `packages.find.exclude/include` may have no effect. c \rSrSr%SrSrSSSS\"\R=(d S54/rS \ S 'S r SS jr SS jr Sr SrSSjrSSjrSrSSjrSSjrSSjrS SjrSrS!SjrS"SjrSrg)#editable_wheelhzBuild 'editable' wheel for development. This command is private and reserved for internal use of setuptools, users should rely on ``setuptools.build_meta`` APIs. zBDO NOT CALL DIRECTLY, INTERNAL ONLY: create PEP 660 editable wheel)z dist-dir=dz-directory to put final built distributions in)zdist-info-dir=Iz(path to a pre-build .dist-info directoryzmode=NzHClassVar[list[tuple[str, str, str]] | list[tuple[str, str | None, str]]] user_optionsc<SUlSUlSUlSUlgN)dist_dir dist_info_dir project_dirr=selfs r?initialize_options!editable_wheel.initialize_optionsxs  ! rBc6URnUR=(d [RUlUR =(d 0Ul[ UR=(d* [RRURS55Ulg)Ndist) distributionsrc_rootoscurdirrY package_dirr rWpathjoin)r[r_s r?finalize_optionseditable_wheel.finalize_options~s_  ==5BII++1rT]]Tbggll4;K;KV.TU rBcURRSS9 UR5 URS5 UR S5nUR UR 5 URU5 g![aXnURR=(d URR5n[R"USUS35 eSnAff=f)NT)exist_ok bdist_wheelz3An error occurred when building editable wheel for zl. See debugging tips in: https://setuptools.pypa.io/en/latest/userguide/development_mode.html#debugging-tips)rWmkdir_ensure_dist_inforeinitialize_commandget_finalized_commandwrite_wheelfilerX_create_wheel_file Exceptionr`nameget_nameradd_note)r[rkexprojects r?runeditable_wheel.runs  MM    .  " " $  % %m 444]CK  ' '(:(: ;  # #K 0 '',,L0A0A0J0J0LG NNEgYOff   sA7A:: CACCcURcb[[URS55nURUlUR 5 UR5 URUlg[UR5RS5(de[URS5R5(deg)Nr%z .dist-infoMETADATA) rXr dist_info_clsrnrW output_dirensure_finalizedrxstrendswithr exists)r[r%s r?rm editable_wheel._ensure_dist_infos    %]D,E,Ek,RSI#'==I  & & ( MMO!*!8!8D t))*33LAA AA**J7>>@@ @@rBcURnUR(dg[URURR SS55R 5n[X1X$5nUR5 g)NrS.) r`namespace_packagesr rYrdgetresolve_NamespaceInstallerinstall_namespaces)r[installation_dir pth_prefixr_ra installers r?_install_namespaces"editable_wheel._install_namespacess_  && (($*:*:*>*>r3*GHPPR' U $$&rBcUR(a[UR5RO [5n[[UR S55n[ US5$)Nz *.egg-info)rXr parentmaprglobnext)r[ parent_dir candidatess r?_find_egg_info_dir!editable_wheel._find_egg_info_dirsH8<8J8JT$,,-44PTPV jool;< J%%rBcURn[U5n[U5n[[X!S3S55n[[X!S3S55n[[X!S3S55n [[UR SSS95n [U5U lSU l[[UR SSS95n [[UR S SS95n U=U l =U l U l U=U l =U lU lU =U lU lXlX|lUR)S 5n S U l[[,UR)S 55nSUl[U5U l[[2UR)S 55nSUlUR75UlUR;5 U R=5 U R=5 g)aConfigure commands to behave in the following ways: - Build commands can write to ``build_lib`` if they really want to... (but this folder is expected to be ignored and modules are expected to live in the project directory...) - Binary extensions should be built in-place (editable_mode = True) - Data/header/script files are not part of the "editable" specification so they are written directly to the unpacked_wheel directory. z.datadataheadersscriptsr&T)reinit_subcommandsr#r' build_scriptspythonr(r$FN)r`rr r egg_info_clsrnegg_baseignore_egg_info_in_manifest build_cls install_cls build_platlib build_purelib build_libinstall_purelibinstall_platlib install_libr(rinstall_headers install_dataget_command_obj executableinstall_scripts_clsno_ep build_temp build_py_clscompilerexisting_egg_info_dir_set_editable_moder~)r[rsunpacked_wheelrtmp_dirr_wheelrrrr&r#r'rr(r$s r?_configure_buildeditable_wheel._configure_builds  N# N 4&?@d>V5>9EFd>V5>9EF $33JSW3X  L/3, t00T0R  229QU2V GPOOe1EORWWW'"9G 1~rBcURXX45 UR5 UR5upVURS5 URS5 URS5 XV4$)Nrrr)r_run_build_subcommandsr _run_install)r[ dist_namerrrrrs r?_run_build_commands"editable_wheel._run_build_commands sb iL ##%446 )$ )$ &!~rBcURS5nUR5HPnURU5nUS:Xa%[U5[LaUR U5 M?UR U5 MR g)aE Issue #3501 indicates that some plugins/customizations might rely on: 1. ``build_py`` not running 2. ``build_py`` always copying files to ``build_lib`` However both these assumptions may be false in editable_wheel. This method implements a temporary workaround to support the ecosystem while the implementations catch up. r#r$N)rortyper _safely_run run_command)r[r#rsrs r?r%editable_wheel._run_build_subcommandssf**73**,D,,T2Cz!d3i|&C  &  & -rBc URU5$![a7 [R"SS[R "5SUSUS35 gf=f)Nz0Customization incompatible with editable installz z If you are seeing this warning it is very likely that a setuptools plugin or customization overrides the `a` command, without taking into consideration how editable installs run build steps starting from setuptools v64.0.0. Plugin authors and developers relying on custom build steps are encouraged to update their `aa` implementation considering the information about editable installs in https://setuptools.pypa.io/en/latest/userguide/extension.html. For the time being `setuptools` will silence this error and ignore the faulty command, but this behavior will change in future versions. )rrrr!r; traceback format_exc)r[rs r?reditable_wheel._safely_run0sp ##H- -  ( - -B%%'()89AzB- .6J7  s>AAc SSKJn URS5nURnSR UR 55nSnUSUSUS3n[ URU5nUR5(aUR5 [US9n [SS9n [S S9n U oon[ U [ UR5R5n[R"URU5 URX5 URXLX5unnUR!XEU 5nU U"US 5nU"UUU5 UR#U 5 SSS5 SSS5 SSS5 SSS5 SSS5 U$!,(df  N0=f!,(df  N9=f!,(df  NB=f!,(df  NK=f!,(df  U$=f) Nrr*r%-z 0.editablez.whl)suffixz .build-libz .build-tempw)wheel.wheelfiler+rorsrfget_tagr rWrunlinkr rXshutilcopytreerr_select_strategy write_files)r[rkr+r%rtag build_tag archive_name wheel_pathrr build_tmpunpackedlibtmpunpacked_dist_inforrstrategy wheel_objs r?rq!editable_wheel._create_wheel_fileLs{-..{; NN hh{**,- #Ai[#d; $--6         +<@&l; &m< xc9!%hT5G5G0H0M0M!N  OOD..0B C  $ $X 9!55i3TNE7,,YSAH9Z5E73%%h/6 G Gc[URSU3S5nU(a;U"5(a.[RSUS35 UR SU35 ggg)Nhas_z Installing z as non editableinstall_)getattrr`_loggerinfor)r[category has_categorys r?reditable_wheel._run_installhsXt00D 2CTJ LNN LL;xj0@A B   xz2 3+.&&**2s3Gd//[8R7ST Tt00$77rB)rWrXr=rdrYrENone)rErD)rsrrrrrrr)rE tuple[list[str], dict[str, str]]) rrrrrrrrrEr )rr)rr)rsrrrrrrEEditableStrategy)rFrGrHrIrJ descriptionr r/rT__annotations__r\rgrxrmrrrrrrrrrqrrrMrCrBr?rOrOhs  WK LK $!6!6!<"=>  V * A'& =#=#)0=#=D=#OV=#~ #         * ',884 888 8  8rBrOcR\rSrSrSSjrSSjrS SjrSrg) r icgrVrC)r[rrrs r?__call__EditableStrategy.__call__srBcgrVrCrZs r? __enter__EditableStrategy.__enter__srBcgrVrCr[ _exc_type _exc_value _tracebacks r?__exit__EditableStrategy.__exit__s rBrCN)rr+r list[str]rMapping[str, str]rEobjectrEr))rztype[BaseException] | NonerzBaseException | NonerzTracebackType | NonerEr )rFrGrHrIrrrrMrCrBr?r r sW'0;L %-))   rBr c\\rSrSrSSjrS SjrS SjrS SjrSrg) ric(XlX lX0lgrVr_rs path_entries)r[r_rsr%s r?__init___StaticPth.__init__s  (rBcSRSUR55n[US35nURSURS3U5 g)N c3T# UHn[UR55v M g7frV)rr).0ps r? &_StaticPth.__call__..s H6GC ,,6Gs&(r.pth)rfr% _encode_pthwritestrrs)r[rrrentriescontentss r?r_StaticPth.__call__sI))Hd6G6GHH'"~. tyyk6ArBcS[[[RUR55<S3n[ R U[-5 U$)Nz_ Editable install will be performed using .pth file to extend `sys.path` with: z )listrrbfspathr%rwarning_LENIENT_WARNINGr[msgs r?r_StaticPth.__enter__sH c"))T../ 034   ../ rBcgrVrCrs r?r_StaticPth.__exit__s rBr$N)r_rrsrr%z list[Path]rEr rr+rrrrrEr r!rr rr rr rEr ) rFrGrHrIr&rrrrMrCrBr?rrsa) BB'0B;LB B       rBrc^\rSrSrSrS U4SjjrS U4SjjrS SjrSSSjjrSSjr SSjr SS jr S r U=r $)riaH Creates a ``.pth`` file that points to a link tree in the ``auxiliary_dir``. This strategy will only link files (not dirs), so it can be implemented in any OS, even if that means using hardlinks instead of symlinks. By collocating ``auxiliary_dir`` and the original source code, limitations with hardlinks should be avoided. c>[U5Ul[U5R5UlUR S5R Ul[TU]!XUR/5 g)Nr$) r rrrr copy_file_filesuperr&)r[r_rsrr __class__s r?r&_LinkTree.__init__sV"-0i002))*5??  d&8&8%9:rBcH>URX#5 [TU] XU5 grV) _create_linksrEr)r[rrrrFs r?r_LinkTree.__call__s" 5* w/rBc [[5 [U5R5R UR 5n[ U5R[RS5sSSS5 $!,(df  g=f)N/) r ValueErrorr r relative_torrreplacerbsep)r[fileres r?_normalize_output_LinkTree._normalize_outputsT j !:%%'33DNNCDt9$$RVVS1" ! !s AA55 BcURU- nURR5(dURRSS9 UR X$US9 g)NT)parentslink)rris_dirrlrD)r[relative_outputsrc_filerWdests r? _create_file_LinkTree._create_filesJ!!O3{{!!## KK  d  + 8 -rBc^TRRSSS9 [TR5(aSOSnU4SjUR55nUVVs0sH upVUcM XV_M nnnUH5nTR U5n U (dMX;dM$TR X5 M7 UR5HupTR XUS9 M gs snnf)NT)rUrjsymhardc3N># UHupTRU5U4v M g7frV)rR)r+kvr[s r?r-*_LinkTree._create_links..s%XAWt--a0!4AWs"%rV)rrl_can_symlink_filesitemsrRr\) r[outputsoutput_mapping link_type normalisedrbrcmappingsoutputrelativesrcs ` r?rI_LinkTree._create_linkss    =/0B0BCCE XAUAUAWX %/AZTQ1DADZAF--f5HxH4!!(3 &^^-MH   h)  <.Bs  C&CcBSn[RU[-5 U$)Nz=Strict editable install will be performed using a link tree. )rr8_STRICT_WARNINGr:s r?r_LinkTree.__enter__sNo-. rBcRSURS3n[R"SU5 g)Nz\ Strict editable installation performed using the auxiliary directory: z Please be careful to not remove this directory, otherwise you might not be able to import/use your package. Editable installation.)rr r;r[rrrr;s r?r_LinkTree.__exit__s2     !   5s;rB)rDrr) r_rrsrrrrrrEr r?)rQrrErDrV)rYrrZr)rhrr!r@)rFrGrHrIrJr&rrRr\rIrrrM __classcell__)rFs@r?rrs ; ; ; ;  ;  ;00'00;L0 0 . = < < < <  < .sD$Cbb$CsrSrz.finder)r_rarbrcr r_find_top_level_modulesrd_find_package_rootsdict_find_namespacesr_find_virtual_namespacesrrrsrsafe_identifier) r[ra top_levelrdroots namespaces_pkglegacy_namespacesrrsfinders r? template_vars_TopLevelFinder.template_varss(99%%2.35LTYY5WX ii++1r #IHE  !3!3!9r5AD$>> _simple_layout(['a'], {"": "src"}, "/tmp/myproj") True >>> _simple_layout(['a', 'a.b'], {"": "src"}, "/tmp/myproj") True >>> _simple_layout(['a', 'a.b'], {}, "/tmp/myproj") True >>> _simple_layout(['a', 'a.a1', 'a.a1.a2', 'b'], {"": "src"}, "/tmp/myproj") True >>> _simple_layout(['a', 'a.a1', 'a.a1.a2', 'b'], {"a": "a", "b": "b"}, ".") True >>> _simple_layout(['a', 'a.a1', 'a.a1.a2', 'b'], {"a": "_a", "b": "_b"}, ".") False >>> _simple_layout(['a', 'a.a1', 'a.a1.a2', 'b'], {"a": "_a"}, "/tmp/myproj") False >>> _simple_layout(['a', 'a.a1', 'a.a1.a2', 'b'], {"a.a1.a2": "_a2"}, ".") False >>> _simple_layout(['a', 'a.b'], {"": "src", "a.b": "_ab"}, "/tmp/myproj") False >>> # Special cases, no packages yet: >>> _simple_layout([], {"": "src"}, "/tmp/myproj") True >>> _simple_layout([], {"a": "_a", "": "src"}, "/tmp/myproj") False rSc 3># UH7up[R"[T/URS5Q76U5v M9 g7frN)r same_pathr split)r+keyvaluers r?r-!_simple_layout..s:(JC V5ciin5u==(s?A) rrrbre commonpathr _parent_pathrfall)rrdrYrlayoutrs @r?rrls>PX Xx$S{CCxF X ;B:-- WW   flln E FF  ,,.  YsBchURU5nURS[R-5$)aInfer the parent path containing a package, that if added to ``sys.path`` would allow importing that package. When ``pkg`` is directly mapped into a directory with a different name, return its own path. >>> _parent_path("a", "src/a") 'src' >>> _parent_path("b", "src/c") 'src/c' rL) removesuffixrstriprbrP)rpkg_pathrs r?rrs+ " "3 'F ==rvv &&rBc## [UR=(d /5ShvN UR=(d /nUVs/sH nSU;dM UPM nnUR(aURv OFUR=(d /nX4Vs/sH!nSUR ;dMUR PM# sn- nUHnUR S5un nUv M gNs snfs snf7f)Nr)iterr py_modules ext_package ext_modulesrs rpartition) r_rmodnested_modulesrxmodulepackage_s r?rrsDMM'R(((&BJ%/>Zc3#:cZN> &&," ;H;a#-6166;HH ))#. A !)? Is9"C-C!C- C#C#;C-C()C(9)C-# C-c## UR=(d /nSU5ShvN UR(d'UR=(d /nSU5ShvN ggN=N7f)Nc36# UHnSU;dM Uv M g7frrC)r+rs r?r-*_find_top_level_modules..s>#ejj011rBc #"# UHnSU;aM URS5n[[U5S- SS5HLnSRUSU5n[ [ X@S55nUR 5(aX@;dMHUv MN M g7f)aBy carefully designing ``package_dir``, it is possible to implement the logical structure of PEP 420 in a package without the corresponding directories. Moreover a parent package can be purposefully/accidentally skipped in the discovery phase (e.g. ``find_packages(include=["mypkg.*"])``, when ``mypkg.foo`` is included by ``mypkg`` itself is not). We consider this case to also be a virtual namespace (ignoring the original directory) to emulate a non-editable installation. This function will try to find these kinds of namespaces. rr"rNrS)rrangelenrfr rr)rrpartsi partial_nameres r?rrs c>  #s5zA~q"-A88E"1I.L),2FGD;;==L$A"" . s A# UH upTU:g=(a [TTX5v M" g7frV) _is_nested)r+other other_pathrers r?r-!_remove_nested..s0 %6! 5L EZT5E E%6s(+)rcopyreversedr6rfanypop)rrlrers @@r?rrsh ).." #Fd9??#456 T  %.__%6    JJsO 7 MrBc[R"U5nURUSS5RS5R S5nUR U5=(a# U[R"[ U/UQ765:H$)au Return ``True`` if ``pkg`` is nested inside ``parent`` both logically and in the file system. >>> _is_nested("a.b", "path/a/b", "a", "path/a") True >>> _is_nested("a.b", "path/a/b", "a", "otherpath/a") False >>> _is_nested("a.b", "path/a/b", "c", "path/c") False >>> _is_nested("a.a", "path/a/a", "a", "path/a") True >>> _is_nested("b.a", "path/b/a", "a", "path/a") False rSr"r)rnormpathrOstripr startswithr )rrr parent_path norm_pkg_pathrests r?rrsoNN8,M ;;vr1 % + +C 0 6 6s ;D >>& ! mu~~ [ 4 8'rBc\[R"USS9 [R"U5 U$)zFCreate a directory ensured to be empty. Existing files may be removed.T) ignore_errors)rrmtreerbmakedirs)dir_s r?rrs! NN4t,KK KrBc*\rSrSrSSjrSrSrSrg)ricBXlX@lX lX0l/UlgrV)r`rar editable_namerg)r[r`rrras r?r&_NamespaceInstaller.__init__ s ( 0*"$ rBc[RRURURUR -5$)zInstallation target.)rbrerfrr nspkg_extrZs r?_get_nspkg_file#_NamespaceInstaller._get_nspkg_file's,ww||D1143E3E3VWWrBc>[[UR55$)z1Where the modules/packages should be loaded from.)reprrrarZs r? _get_root_NamespaceInstaller._get_root+sC &''rB)r`rrrgraNr )rFrGrHrIr&rrrMrCrBr?rrs%X(rBra from __future__ import annotations import sys from importlib.machinery import ModuleSpec, PathFinder from importlib.machinery import all_suffixes as module_suffixes from importlib.util import spec_from_file_location from itertools import chain from pathlib import Path MAPPING: dict[str, str] = {mapping!r} NAMESPACES: dict[str, list[str]] = {namespaces!r} PATH_PLACEHOLDER = {name!r} + ".__path_hook__" class _EditableFinder: # MetaPathFinder @classmethod def find_spec(cls, fullname: str, path=None, target=None) -> ModuleSpec | None: # type: ignore # Top-level packages and modules (we know these exist in the FS) if fullname in MAPPING: pkg_path = MAPPING[fullname] return cls._find_spec(fullname, Path(pkg_path)) # Handle immediate children modules (required for namespaces to work) # To avoid problems with case sensitivity in the file system we delegate # to the importlib.machinery implementation. parent, _, child = fullname.rpartition(".") if parent and parent in MAPPING: return PathFinder.find_spec(fullname, path=[MAPPING[parent]]) # Other levels of nesting should be handled automatically by importlib # using the parent path. return None @classmethod def _find_spec(cls, fullname: str, candidate_path: Path) -> ModuleSpec | None: init = candidate_path / "__init__.py" candidates = (candidate_path.with_suffix(x) for x in module_suffixes()) for candidate in chain([init], candidates): if candidate.exists(): return spec_from_file_location(fullname, candidate) return None class _EditableNamespaceFinder: # PathEntryFinder @classmethod def _path_hook(cls, path) -> type[_EditableNamespaceFinder]: if path == PATH_PLACEHOLDER: return cls raise ImportError @classmethod def _paths(cls, fullname: str) -> list[str]: paths = NAMESPACES[fullname] if not paths and fullname in MAPPING: paths = [MAPPING[fullname]] # Always add placeholder, for 2 reasons: # 1. __path__ cannot be empty for the spec to be considered namespace. # 2. In the case of nested namespaces, we need to force # import machinery to query _EditableNamespaceFinder again. return [*paths, PATH_PLACEHOLDER] @classmethod def find_spec(cls, fullname: str, target=None) -> ModuleSpec | None: # type: ignore if fullname in NAMESPACES: spec = ModuleSpec(fullname, None, is_package=True) spec.submodule_search_locations = cls._paths(fullname) return spec return None @classmethod def find_module(cls, _fullname) -> None: return None def install(): if not any(finder == _EditableFinder for finder in sys.meta_path): sys.meta_path.append(_EditableFinder) if not NAMESPACES: return if not any(hook == _EditableNamespaceFinder._path_hook for hook in sys.path_hooks): # PathEntryFinder is needed to create NamespaceSpec without private APIS sys.path_hooks.append(_EditableNamespaceFinder._path_hook) if PATH_PLACEHOLDER not in sys.path: sys.path.append(PATH_PLACEHOLDER) # Used just to trigger the path hook c[[UR5[R"S5S95n[ R XUS9$)zWCreate a string containing the code for the``MetaPathFinder`` and ``PathEntryFinder``. r)rrsrr)rrrfoperator itemgetter_FINDER_TEMPLATEformatrs r?rrs< 6'--/x/B/B1/EFGG  " "* " UUrBc\rSrSrSrSrg)rizCFile system does not seem to support either symlinks or hard links.rCN)rFrGrHrIrJrMrCrBr?rrsMrBr)rrrEr)rr rEbool)r Iterable[str]rddict[str, str]rYrrEr)r_rrE Iterator[str])rrrdrrarrEr)rerrEr)rrrEr)rrrrrEzIterator[tuple[str, list[str]]])rrrEr) rrrrrrrrrEr)rr,rEr,)rsrrrrzdict[str, list[str]]rEr)crJ __future__rrloggingr rbrrcollections.abcrrr contextlibrenumrinspectr itertoolsr r pathlibr tempfiler typesrtypingrrrrrrSrrrrrrrr3rr discoveryrr_rwarningsr r!r#rr$rr%r|r&rr'rr(rtyping_extensionsr)_vendor.wheel.wheelfiler+r, getLoggerrFrr/rqr9rOr rrrr0rerrrrrrrrrrr Installerrr r FileErrorrrCrBr?r$s #  77$'CCJJ!)D%.1.+C&3 T!   H %&$D&$R ^8W^8B x   <>