_dց 2dZddlZddlZddlZddlZddlZddlZddlmZddl m Z ddl m Z ddl mZddlmZddlmZdd lmZmZmZmZmZmZmZmZmZmZd d lmZm Z m!Z!m"Z"m#Z#d d l$m%Z%d d l&m'Z'd dl(m)Z)m*Z*m+Z+ddl,m,Z-erddl.m/Z/ej`dk\rddlm1Z1nerddl2m1Z1nddl3m4Z1ee5efZ6ede6Z7ejpe9Z:Gdde Z;dZGdde1Z?Gdd Z@Gd!d"e@ZAGd#d$ZBd%e5d&eCfd'ZDd(ed&eEfd)ZFd*ee5d+ee5e5fd,ed&eEfd-ZGd.ZHd/e'd&ee5fd0ZId/e'd&ee5fd1ZJd*ee5d+ee5e5fd2e6d&ee5e5ffd3ZKd4e6d&e5fd5ZLd6ee5e5fd&ee5fd7ZMd*ee5d6ee5e5fd&eee5ee5ffd8ZNd6ee5e5fd&ee5e5ffd9ZOd:e5d;e5dZPd?e7d&e7fd@ZQGdAdBe#jZSdCZTdDe5dEee5e5fdFee5ee5fd&e5fdGZUGdHdIe"jZWGdJdKe+ZXy)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``. N)suppress)Enum)cleandoc)chain)Path)TemporaryDirectory) TYPE_CHECKINGDictIterableIteratorListMappingOptionalTupleTypeVarUnion)Command_normalization_patherrors namespaces)find_package_path) Distribution)InformationOnlySetuptoolsDeprecationWarningSetuptoolsWarning)build_py WheelFile))Protocol)ABC_P)boundc<eZdZdZdZdZdZedee ddfdZ y) _EditableModea 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). strictlenientcompatmodereturnc|stjS|j}|tjvrt j d|d|dk(rt jdddt|S)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. userguide/development_mode.html)see_docs)r)LENIENTupper __members__r OptionErrorremit)clsr-_modes C/usr/lib/python3/dist-packages/setuptools/command/editable_wheel.pyconvertz_EditableMode.convertQsv (( (   11 1$$'>thFV%WX X H  ( - -* ;  U##N) __name__ __module__ __qualname____doc__STRICTr3r0 classmethodrstrr;r<r:r)r)Es<FG F$8C=$_$$r<r)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. c2eZdZdZdZddddeejxsdfgZdZd Z d Z d Z d Z d e efdZdedededefdZdZd eeeeeefffdZdedededed eeeeeefff dZdZdefdZdZdefdZdededed dfd Zy)!editable_wheelzBuild '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=Nc<d|_d|_d|_d|_yN)dist_dir dist_info_dir project_dirr-selfs r:initialize_optionsz!editable_wheel.initialize_optionss  ! r<c|j}|jxstj|_|j xsi|_t |jxs*tjj|jd|_y)Ndist) distributionsrc_rootoscurdirrN package_dirrrLpathjoin)rPrSs r:finalize_optionszeditable_wheel.finalize_optionss_  ==5BII++1rT]]Tbggll4;K;KV.TU r<c |jjd|j|jd|j d}|j |j |j|y#t$r^tj|jjxs|jj}tj|wxYw)NT)exist_ok bdist_wheel)project)rLmkdir_ensure_dist_inforeinitialize_commandget_finalized_commandwrite_wheelfilerM_create_wheel_file Exception traceback print_excrTnameget_name_DebuggingTipsr7)rPr^r_s r:runzeditable_wheel.runs  MM    .  " " $  % %m 444]CK  ' '(:(: ;  # #K 0     !'',,L0A0A0J0J0LG     0   s A:A==A'C$c\|jT|jd}|j|_|j |j |j|_yt |jjdsJt|jdjsJy)N dist_infoz .dist-infoMETADATA) rMrbrL output_dirensure_finalizedrlrCendswithrexists)rPrns r:raz editable_wheel._ensure_dist_infos    %11+>I#'==I  & & ( MMO!*!8!8D t))*33LA AA**J7>>@ @@r<c|j}|jsyt|j|jj ddj }t||||}|jy)NrI.) rTnamespace_packagesrrNrXgetresolve_NamespaceInstallerinstall_namespaces)rPinstallation_dir pth_prefixrSrU installers r:_install_namespacesz"editable_wheel._install_namespacessd  && (($*:*:*>*>r3*GHPPR'.> HU $$&r<r.c|jrt|jjn t}tt|j d}t |dS)Nz *.egg-info)rMrparentmaprCglobnext)rP parent_dir candidatess r:_find_egg_info_dirz!editable_wheel._find_egg_info_dirsH8<8J8JT$,,-44PTPV jool;< J%%r<riunpacked_wheel build_libtmp_dirc|j}t|}t|}tt||dd}tt||dd}tt||dd} |jdd} t|| _d| _|jdd} |jd d} |x| _x| _| _|x| _ x| _ | _ | x| _ | _ || _|| _|j!d } d| _t|| _|j!d }d |_|j)|_|j-| j/| j/y )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.datadataheadersscriptsegg_infoT)reinit_subcommandsbuildinstallinstall_scriptsrFN)rTrCrrbegg_baseignore_egg_info_in_manifest build_platlib build_purelibrinstall_purelibinstall_platlib install_libr build_scriptsinstall_headers install_dataget_command_objno_ep build_tempcompilerexisting_egg_info_dir_set_editable_moderq)rPrirrrrSwheelrrrrrrrrs r:_configure_buildzeditable_wheel._configure_builds  N# N 44&?@d>dV5>9EFd>dV5>9EF,,ZD,QL/3,))'d)K++I$+OFOOOe1EORWWW'"9Gg}i}|jd}|jD]r}|j|}t|dr#|j|j xsgt|dsP|j |j xsit||fS)Nr get_outputsget_output_mapping)rcrrextendrupdater)rPfilesmappingrrrs r:_collect_build_outputsz%editable_wheel._collect_build_outputss"$**73..0 ?H,,X6CsM* S__.4"5s01s557=2>  ?g~r< dist_namec|j|||||j|j\}}|jd|jd|jd||fS)Nrrr)r_run_build_subcommandsr _run_install)rPrrrrrrs r:_run_build_commandsz"editable_wheel._run_build_commandssj iGL ##%446w )$ )$ &!g~r<c|jd}|jD]M}|j|}|dk(r$t|tk7r|j |=|j |Oy)a} 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. rrN)rcrtype build_py_cls _safely_run run_command)rPrrirs r:rz%editable_wheel._run_build_subcommandssk33G<**, 'D,,T2Cz!d3i<&?  &  &  'r<rc  |j|S#t$r5tjddt j d|d|dYywxYw)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 `ab` 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 behaviour will change in future versions. )rrfrr7rg format_exc)rPrs r:rzeditable_wheel._safely_run)sp ##H- -  ( - -B%%'()89AzB- .6J7  s;AAc ddlm}|jd}|j}dj |j }d}|d|d|d}t |j|}|jr|jt|} td} td } | 5} | 5} | 5}t | t |jj}tj|j||j| |j|j|| | |\}}|j!||| }|5||d 5}|||||j#| ddddddddddddddd|S#1swY+xYw#1swY/xYw#1swY3xYw#1swY7xYw#1swY|SxYw) Nrr rn-z 0.editablez.whl)suffixz .build-libz .build-tempw)wheel.wheelfiler!rcrirZget_tagrrLrsunlinkrrMshutilcopytreer~r_select_strategy write_files)rPr^r!rnrtag build_tag archive_name wheel_pathrr build_tmpunpackedlibtmpunpacked_dist_inforrstrategy wheel_objs r:rez!editable_wheel._create_wheel_fileEs-..{; NN hh{**,- #Ai[#d; $--6        +<@&l; &m<  0x 0c9 0!%hT5G5G0H0M0M!N  OOD..0B C  $ $Xy~~ >!55i3PSTNE7,,YSAH 09Z5 0E73%%h/ 0 0  0 0 0  0 0 0 0  0 0 0 0 0sm,G/F82BF, F F *F 2F,:F8GFF F) %F,,F5 1F88G =GGcategoryct|jd|d}|r6|r.tjd|d|j d|yyy)Nhas_z Installing z as non editableinstall_)getattrrT_loggerinfor)rPr has_categorys r:rzeditable_wheel._run_installasVt00D 2CTJ LN LL;xj0@A B   xz2 3+|jjdd} t|j|t|| gSt!|j|S)zDDecides which strategy to use to implement an editable installation. __editable__.rrrIru)rrNr)r;r-rA _empty_dir _LinkTreerT_find_packages_simple_layoutrXr0setrw _StaticPth_TopLevelFinder) rPrirr build_namerNr- auxiliary_dirpackageshas_simple_layoutis_compat_modesrc_dirs r:rzeditable_wheel._select_strategygs%TF!C51 4++, $$TYY/ ='' '&tD,<,.&&**2s3Gd//['8R7ST Tt00$77r<)r=r>r?r@ descriptionrr) user_optionsrQr[rlrar~rrCr_Pathrrrr r rrrrrerrrDr<r:rFrFxsA WK LK $!6!6!<"=>L  V " A'&HSM& 0#0#).0#;@0#KP0#d # d3ic3h.G(H   .3 @E PU  tCy$sCx.( ) ',C884S4 888 8  8r<rFc<eZdZdddeedeeeffdZdZdZy) rrr!rrcyrKrD)rPrrrs r:__call__zEditableStrategy.__call__ r<cyrKrDrOs r: __enter__zEditableStrategy.__enter__rr<cyrKrDrP _exc_type _exc_value _tracebacks r:__exit__zEditableStrategy.__exit__rr<N) r=r>r?r rCr rrrrDr<r:rrs3 k $s) d3PS8n   r<rcVeZdZdededeefdZdddeedeeeffd Z d Z d Z y ) rrSri path_entriesc.||_||_||_yrK)rSrir)rPrSrirs r:__init__z_StaticPth.__init__s  (r<rr!rrcdjd|jD}t|d}|jd|jd|y)N c3NK|]}t|jywrK)rCrx).0ps r: z&_StaticPth.__call__..sI!S-Is#%r.pth)rZr _encode_pthwritestrri)rPrrrentriescontentss r:rz_StaticPth.__call__sG))It7H7HIJ'"~. tyyk6Ar<cdtttj|jd}t j |tz|S)Nz_ Editable install will be performed using .pth file to extend `sys.path` with: z )listrrVfspathrrwarning_LENIENT_WARNINGrPmsgs r:rz_StaticPth.__enter__sH c"))T../ 034   ../ r<cyrKrDrs r:rz_StaticPth.__exit__rr<N) r=r>r?rrCr rrr rrrrDr<r:rrsU)\))DJ) BkB$s)Bd3PS8nB  r<rceZdZdZdedededeffd Zddd eed e eefffd Z d ed e efdZ ddedefdZ dZdZdZxZS)ra` 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. rSrirrct||_t|j|_|j dj |_t|!|||jgy)Nr) rrrxrr copy_file_filesuperr)rPrSrirr __class__s r:rz_LinkTree.__init__sX"-0i002))*5??  td&8&8%9:r<rr!rrcL|j||t| |||yrK) _create_linksrr)rPrrrrs r:rz_LinkTree.__call__s$ 5'* w/r<filer.ctt5t|jj |j }t |jtjdcdddS#1swYyxYw)N/) r ValueErrorrrx relative_torrCreplacerVsep)rPrrYs r:_normalize_outputz_LinkTree._normalize_outputs] j ! 2:%%'33DNNCDt9$$RVVS1 2 2 2s AA55A>relative_outputsrc_filec|j|z }|jjs|jjd|j |||y)NT)parentslink)rris_dirr`r)rPr$r%r)dests r: _create_filez_LinkTree._create_filesI!!O3{{!!# KK  d  + 8T -r<c|jjddt|jrdnd}|jDcic]\}}|j ||}}}|j dd|D]-}|j |}|s||vs|j ||/|jD]\}} |j || |ycc}}w)NT)r'r]symhardr()rr`_can_symlink_filesitemsr#popr,) rPoutputsoutput_mapping link_typekvmappingsoutputrelativesrcs r:rz_LinkTree._create_linkss    =/0B0BCE =K=Q=Q=STTQD**1-q0TT T4  4F--f5HHH4!!(F3 4 &^^- =MHc   h)  < =Us CcBd}tj|tz|S)Nz=Strict editable install will be performed using a link tree. )rr_STRICT_WARNINGrs r:rz_LinkTree.__enter__sNo-. r<cPd|jd}tjd|y)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.)rrr7rPrrrrs r:rz_LinkTree.__exit__s2    !   5s;r<rK)r=r>r?r@rrCrrr r rrr#r,rrr __classcell__)rs@r:rrs ; ; ; ;  ;0k0$s)0d3PS8n0chsm.C.3. = .sDb"bDsrz.finderutf-8z.pyzimport z; z .install()r)rSrUrVrWrr_find_top_level_modulesrX_find_package_rootsdict_find_namespacesr_find_virtual_namespacesrirsafe_identifierbytes_finder_templater r) rPrrrrU top_levelrXroots namespaces_rifindercontents r:rz_TopLevelFinder.__call__s99%%2.35LTYY5WX ii++1r #I{HE,0  !3!3!9r5AD$r?rrCrr r rrrrDr<r:rrsJ\AkA$s)Ad3PS8nA* >> _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 rIc 3K|]6\}}tjtg|jd|8ywruN)r same_pathrsplit)rkeyvaluers r:rz!_simple_layout..Zs: C V5ciin5u=sPX Xc$S+{CC XF X ;B:-- WW    O1a!3 O PF  ,,.  Y!Ps BB c|j|r|dt| n|}|jdtjzS)a7Infer 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' Nr)rrlenrstriprVr")rpkg_pathrs r:r}r}`s<'/&7&7&c3#:c>N> &&," ;Ha#-166HH ))#. A )? Is8C CC  CC2C 8C C'C  C c#K|jxsg}d|DEd{|js"|jxsg}d|DEd{yy737w)Nc3*K|] }d|vs| ywrwrD)rrs r:rz*_find_top_level_modules..s<S^.sEq3aff3DAFFEs'')rrr)rSrrs r:rHrH~sZ&BJ>#ejj011r<rc #K|D]y}d|vr|jd}tt|dz ddD]E}dj|d|}t t ||d}|j r||vsB|G{yw)a8By 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. rurrNrI)ryrangerrZrrrs)rrpartsi partial_namerYs r:rLrLs # c>  #s5zA~q"- #A88E"1I.L), 2FGD;;=L $A""  # #s A6B9 Bc#K|D]K}t||d}t|js*t|djrE||gfMyw)NrIz __init__.py)rrrs)rrrrYs r:rKrKsS  i4 :   tD-'@'G'G'I-  s,AA Act|j}tt|j D]:\t fd|j Ds*|j <|S)Nc3NK|]\}}|k7xrt||ywrK) _is_nested)rother other_pathrYrs r:rz!_remove_nested..s4 !z 5L EZT5*E E s"%)rJcopyreversedr r1anyr2)rr9rYrs @@r:rrsh ).." #Fd9??#456 T  %.__%6   JJsO  Mr<rrr parent_pathctj|}|j|ddjdj d}|j |xr"|tjt |g|k(S)a 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 rIrru)rnormpathr!stripry startswithr)rrrr norm_pkg_pathrests r:rrsoNN8,M ;;vr1 % + +C 0 6 6s ;D >>& ! mu~~ [ 4 8'r<dir_c^tj|dtj||S)zFCreate a directory ensured to be empty. Existing files may be removed.T) ignore_errors)rrmtreerVmakedirs)rs r:rrs! MM$d+KK Kr<ceZdZdZdZdZy)rycX||_||_||_||_g|_d|_y)NF)rTrUr{ editable_namer3dry_run)rPrTr{rrUs r:rz_NamespaceInstaller.__init__s/(  0*  r<cjtjj|j|jS)zInstallation target.)rVrYrZr{rrOs r: _get_targetz_NamespaceInstaller._get_targets#ww||D1143E3EFFr<c>tt|jS)z1Where the modules/packages should be loaded from.)reprrCrUrOs r: _get_rootz_NamespaceInstaller._get_rootsC &''r<N)r=r>r?rrrrDr<r:ryrysG(r<rya 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 = {mapping!r} NAMESPACES = {namespaces!r} PATH_PLACEHOLDER = {name!r} + ".__path_hook__" class _EditableFinder: # MetaPathFinder @classmethod def find_spec(cls, fullname, path=None, target=None): # 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, candidate_path): 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) class _EditableNamespaceFinder: # PathEntryFinder @classmethod def _path_hook(cls, path): if path == PATH_PLACEHOLDER: return cls raise ImportError @classmethod def _paths(cls, fullname): # Ensure __path__ is not empty for the spec to be considered a namespace. return NAMESPACES[fullname] or MAPPING.get(fullname) or [PATH_PLACEHOLDER] @classmethod def find_spec(cls, fullname, target=None): 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): 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 rirrc|tt|jd}tj |||S)z_Create a string containing the code for the``MetaPathFinder`` and ``PathEntryFinder``. c |dS)NrrD)rs r:z"_finder_template..Ss 1r<)rzrirr)rJrr1_FINDER_TEMPLATEformatrs r:rOrOMs3 6'--/~>?G  " "g* " UUr<ceZdZdZy)rqzCFile system does not seem to support either symlinks or hard links.N)r=r>r?r@rDr<r:rqrqWsMr<rqceZdZdZdZdZy)rkz!Problem in editable installation.a  An error happened while installing `{project}` in editable mode. The following steps are recommended to help debug this problem: - Try to install the project normally, without using the editable mode. Does the error still persist? (If it does, try fixing the problem before attempting the editable mode). - If you are using binary extensions, make sure you have all OS-level dependencies installed (e.g. compilers, toolchains, binary libraries, ...). - Try the latest version of setuptools (maybe the error was already fixed). - If you (or your project dependencies) are using any setuptools extension or customization, make sure they support the editable mode. After following the steps above, if the problem still persists and you think this is related to how setuptools handles editable installations, please submit a reproducible example (see https://stackoverflow.com/help/minimal-reproducible-example) to: https://github.com/pypa/setuptools/issues r1N)r=r>r?_SUMMARY_DETAILS _SEE_DOCSrDr<r:rkrk[s2HH*2Ir<rk)Yr@loggingr\rVrrZrg contextlibrenumrinspectr itertoolsrpathlibrtempfilertypingr r r r r rrrrrrIrrrrr discoveryrrSrwarningsrrrrrrr!r[r$typing_extensionsabcr%rCrr& getLoggerr=rr)r=rrFrrrrrNrboolr0rr}rrHrIrrLrKrrr InstallerryrrO FileErrorrqrkrDr<r:rs  '   * /)v*# c4i T '  H %&$D&$R G8WG8T x   .C< C