o 0ήcy @sdZddlZddlZddlZddlZddlZddlZddlZddlm Z ddl m Z ddl m Z ddlmZddlmZddlmZdd lmZmZmZmZmZmZmZmZmZmZdd lm Z m!Z!m"Z"m#Z#dd l$m%Z&dd l'm(Z(dd l)m*Z*erddl+m,Z,ej-dkrddlm.Z.nerddl/m.Z.nddl0m1Z.ee2efZ3ede3dZ4e5e6Z7Gddde Z8dZ9dZ:Gddde Z;Gddde.ZGd d!d!Z?d"ed#e@fd$d%ZAd&ee2d'ee2e2fd(ed#e@fd)d*ZBd+d,ZCd-e*d#ee2fd.d/ZDd-e*d#ee2fd0d1ZEd&ee2d'ee2e2fd2e3d#ee2e2ffd3d4ZFd5e3d#e2fd6d7ZGd8ee2e2fd#ee2fd9d:ZHd&ee2d8ee2e2fd#eee2ee2ffd;d<ZId8ee2e2fd#ee2e2ffd=d>ZJd?e2d@e2dAe2dBe2d#e@f dCdDZKdEe3d#e2fdFdGZLdHe4d#e4fdIdJZMdKe2d#e2fdLdMZNGdNdOdOe#jOZPdPZQdKe2dQee2e2fdRee2ee2fd#e2fdSdTZRGdUdVdVeSZTGdWdXdXe"jUZVdS)Ya 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)CommandSetuptoolsDeprecationWarningerrors namespaces)build_pyfind_package_path) Distribution WheelFile))Protocol)ABC_P)boundc@s6eZdZdZdZdZdZedee ddfddZ d S) _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). strictlenientcompatmodereturncCsN|stjS|}|tjvrtd|d|dkr#d}t|tt|S)NzInvalid editable mode: z. Try: 'strict'.COMPATax 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. For more information, please check: https://setuptools.pypa.io/en/latest/userguide/development_mode.html ) r"LENIENTupper __members__r OptionErrorwarningswarnr)clsr&_modemsgr2H/tmp/pip-target-vg8gfxp4/lib/python/setuptools/command/editable_wheel.pyconvertGs  z_EditableMode.convertN) __name__ __module__ __qualname____doc__STRICTr)r( classmethodrstrr4r2r2r2r3r";sr"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@s$eZdZdZdZddddeejpdfgZdd Zd d Z d d Z ddZ ddZ de efddZdedededefddZddZdeeeeeefffddZdededededeeeeeefff d d!Zd"d#Zd$efd%d&Zd'd(Zd)efd*d+Zded,ededd-fd.d/ZdS)0editable_wheelzkBuild 'editable' wheel for development. (This command is reserved for internal use of setuptools). z!create a 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=NcCsd|_d|_d|_d|_dSN)dist_dir dist_info_dir project_dirr&selfr2r2r3initialize_optionsvs z!editable_wheel.initialize_optionscCs@|j}|jptj|_|jpi|_t|jptj |jd|_dS)Ndist) distributionsrc_rootoscurdirrC package_dirrrApathjoin)rErGr2r2r3finalize_options|s  zeditable_wheel.finalize_optionsc Cs|z#|jjdd||d|d}||j||WdSty=}zt d}t t ||d}~ww)NT)exist_ok bdist_wheela Support for editable installs via PEP 660 was recently introduced in `setuptools`. If you are seeing this error, please report to: https://github.com/pypa/setuptools/issues Meanwhile you can try the legacy behavior by setting an environment variable and trying to install again: SETUPTOOLS_ENABLE_FEATURES="legacy-editable" )rAmkdir_ensure_dist_inforeinitialize_commandget_finalized_commandwrite_wheelfilerB_create_wheel_file Exception traceback print_excr InternalErrorr)rErQexr1r2r2r3runs    zeditable_wheel.runcCsd|jdur|d}|j|_|||j|_dSt|jds&Jt|jd s0JdS)N dist_infoz .dist-infoMETADATA) rBrTrA output_dirensure_finalizedr]r;endswithrexists)rEr^r2r2r3rSs   z editable_wheel._ensure_dist_infocCsD|j}|jsdSt|j|jdd}t||||}|dS)Nr?.) rHnamespace_packagesrrCrLgetresolve_NamespaceInstallerinstall_namespaces)rEinstallation_dir pth_prefixrGrI installerr2r2r3_install_namespacess  z"editable_wheel._install_namespacesr'cCs2|jr t|jjnt}tt|d}t|dS)Nz *.egg-info)rBrparentmapr;globnext)rE parent_dir candidatesr2r2r3_find_egg_info_dirs z!editable_wheel._find_egg_info_dirnameunpacked_wheel build_libtmp_dircCs|j}t|}t|}tt||dd}tt||dd}tt||dd} |jddd} t|| _d| _|jddd} |jd dd} || _| _| _|| _ | _ | _ | | _ | _ || _|| _|d } d| _t|| _|d }d |_||_|| | d S)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)rHr;rrTegg_baseignore_egg_info_in_manifest build_platlib build_purelibrwinstall_purelibinstall_platlib install_libr build_scriptsinstall_headers install_dataget_command_objno_ep build_tempcompilertexisting_egg_info_dir_set_editable_modera)rErurvrwrxrGwheelryrzr{r|r~rrrr2r2r3_configure_builds2       zeditable_wheel._configure_buildcCsN|j}|d}|D]}||}t|drd|_q t|dr$d|_q dS)z8Set the ``editable_mode`` flag in the build sub-commandsr~ editable_modeTinplaceN)rHrget_sub_commandshasattrrr)rErGr~cmd_namecmdr2r2r3rs     z!editable_wheel._set_editable_modecCsjg}i}|d}|D]#}||}t|dr"||p gt|dr0||p.iq ||fS)Nr~ get_outputsget_output_mapping)rUrrextendrupdater)rEfilesmappingr~rrr2r2r3_collect_build_outputss     z%editable_wheel._collect_build_outputs dist_namecCsJ|||||||\}}|d|d|d||fS)Nrzr{ry)r_run_build_subcommandsr _run_install)rErrvrwrxrrr2r2r3_run_build_commandss    z"editable_wheel._run_build_commandscCsP|d}|D]}||}|dkr t|tkr ||q ||q dS)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. r~rN)rUrtype build_py_cls _safely_run run_command)rEr~rurr2r2r3r s     z%editable_wheel._run_build_subcommandsrc CsLz||WSty%td|d|d}tj|tddYdSw)Nz If you are seeing this warning it is very likely that a setuptools plugin or customization overrides the `z` command, without taking into consideration how editable installs run build steps starting from v64.0.0. Plugin authors and developers relying on custom build steps are encouraged to update their `aO` implementation considering the information in https://setuptools.pypa.io/en/latest/userguide/extension.html about editable installs. For the time being `setuptools` will silence this error and ignore the faulty command, but this behaviour will change in future versions. ) stacklevel)rrXrY format_excr-r.r)rErr1r2r2r3r"s   zeditable_wheel._safely_runc Csddlm}|d}|j}d|}d}|d|d|d}t|j|}|r0| t |d} t dd} t d d} | } | t} | b}t| t|j j}t |j ||| |j||| | |\}}|||| }|(||d }|||||| Wdn1swYWdn1swYWdn1swYWdn1swYWd|SWd|S1swY|S) Nrrr^-z 0.editablez.whl)suffixz .build-libz .build-tempw)wheel.wheelfilerrUrurNget_tagrrArcunlinkrrBshutilcopytreermr_select_strategy write_files)rErQrr^rtag build_tag archive_name wheel_pathrvrw build_tmpunpackedlibtmpunpacked_dist_inforrstrategy wheel_objr2r2r3rW6sB        (   z!editable_wheel._create_wheel_filecategorycCsLt|jd|d}|r"|r$td|d|d|dSdSdS)Nhas_z Installing z as non editableinstall_)getattrrH_loggerinfor)rEr has_categoryr2r2r3rRs  zeditable_wheel._run_installrEditableStrategyc Csd|d|}t|j}t|j}|tjur)tt|jd|}t|j|||St |j}t ||j |} |tj u} t |j dhkrD| sF| rX|j dd} t|j|t|| gSt|j|S)zDDecides which strategy to use to implement an editable installation. __editable__.rr~r?rd)rrCr"r4r&r9 _empty_dir _LinkTreerH_find_packages_simple_layoutrLr(setrf _StaticPth_TopLevelFinder) rErurrw build_namerCr& auxiliary_dirpackageshas_simple_layoutis_compat_modesrc_dirr2r2r3rXs      zeditable_wheel._select_strategy)r5r6r7r8 descriptionrr" user_optionsrFrOr]rSrmrr;rt_Pathrrrr r rrrrrWrrr2r2r2r3r<is`   2"   r<c@s>eZdZdddeedeeeffddZddZd d Zd S) rrrrrcCdSr@r2rErrrr2r2r3__call__tzEditableStrategy.__call__cCrr@r2rDr2r2r3 __enter__wrzEditableStrategy.__enter__cCrr@r2rE _exc_type _exc_value _tracebackr2r2r3__exit__zrzEditableStrategy.__exit__N) r5r6r7r r;r rrrr2r2r2r3rss" rc@sXeZdZdededeefddZdddeed eeeffd d Z d d Z ddZ dS)rrGru path_entriescCs||_||_||_dSr@)rGrur)rErGrurr2r2r3__init__s z_StaticPth.__init__rrrrcCs@ddd|jD}t|dd}|d|jd|dS)N css|] }t|VqdSr@)r;rg).0pr2r2r3 z&_StaticPth.__call__..utf-8r.pth)rNrbyteswritestrru)rErrrentriescontentsr2r2r3rsz_StaticPth.__call__cCs,dtttj|jd}t|t|S)Nz_ Editable install will be performed using .pth file to extend `sys.path` with: z )listrorJfspathrrwarning_LENIENT_WARNINGrEr1r2r2r3rs z_StaticPth.__enter__cCrr@r2rr2r2r3rrz_StaticPth.__exit__N) r5r6r7rr;r rrr rrrr2r2r2r3r~s " rcseZdZdZdedededeffdd Zdd d eed e eefffd d Z dede efddZ ddedefddZ ddZddZddZZS)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. rGrurrwcs>t||_t||_|dj|_t|||jgdS)Nr) rrrgrwr copy_file_filesuperr)rErGrurrw __class__r2r3rs z_LinkTree.__init__rrrrcs |||t|||dSr@) _create_linksrrrrr2r3rs z_LinkTree.__call__filer'cCsRttt||j}t|tj dWdS1s"wYdS)N/) r ValueErrorrrg relative_torwr;replacerJsep)rErrMr2r2r3_normalize_outputs  z_LinkTree._normalize_outputNrelative_outputsrc_filecCs6|j|}|js|jjdd|j|||ddS)NT)parentslink)rrnis_dirrRr)rErrrdestr2r2r3 _create_files  z_LinkTree._create_filecsjjdddtjrdnd}fdd|D}|dd|D]}|}|r7||vr7||q$|D] \}}j|||dqs z+_LinkTree._create_links..r)rrR_can_symlink_filesitemspoprr )rEoutputsoutput_mapping link_typemappingsoutputrelativesrcr2rDr3rs     z_LinkTree._create_linkscCd}t|t|S)Nz=Strict editable install will be performed using a link tree. )rr_STRICT_WARNINGrr2r2r3rz_LinkTree.__enter__cCsd|jd}t|tdS)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. )rr-r.InformationOnlyrErrrr1r2r2r3rsz_LinkTree.__exit__r@)r5r6r7r8rr;rrr r rrrr rrr __classcell__r2r2rr3rs" & rc@sPeZdZdedefddZdddeedeeeffd d Zd d Z d dZ dS)rrGrucCs||_||_dSr@)rGru)rErGrur2r2r3rs z_TopLevelFinder.__init__rrrrc Cs|jjptj}tt|jt|j}|jjpi}t|||}t tt |jj p&g|ddt |D}d|j d} t| } tt| ||d} || d| td| d| d d} |d|j d | dS) Ncss|]}|gfVqdSr@r2)rnsr2r2r3rsz+_TopLevelFinder.__call__..rz.finderrz.pyzimport z; z .install()r)rGrIrJrKrr_find_top_level_modulesrL_find_package_rootsdict_find_namespacesr_find_virtual_namespacesru_make_identifierr_finder_templater) rErrrrI top_levelrLroots namespaces_rufindercontentr2r2r3rs  z_TopLevelFinder.__call__cCr)Nz=Editable install will be performed using a meta path finder. )rrrrr2r2r3rrz_TopLevelFinder.__enter__cCsd}t|tdS)Nz Please be careful with folders in your working directory with the same name as your package as they may take precedence during imports. )r-r.rrr2r2r3rsz_TopLevelFinder.__exit__N) r5r6r7rr;rr r rrrr2r2r2r3rs " rbase_dirr'c Cstt|do}t|dt|d}}|jdddtttt)t ||| rD|j dddkrD WdWddSWdn1sNwYzt ||Wntyn}zd}t||d}~ww Wdd S1s{wYdS) N)dirz file1.txtz file2.txtfile1r)encodingTzFile system does not seem to support either symlinks or hard links. Strict editable installs require one of them to be supported.F)rr;rgr write_textrAttributeErrorNotImplementedErrorOSErrorrJsymlink is_symlink read_textrrXLinksNotSupported)r-rpath1path2r\r1r2r2r3rs*   $rrrLrCcs^fdd|D}|stidhfvStjdd|Dtfdd|DS)a[Return ``True`` if: - all packages are contained by the same parent directory, **and** - all packages become importable if the parent directory is added to ``sys.path``. >>> _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 csi|] }|t|qSr2rrpkg)rLrCr2r3r4s z"_simple_layout..r?cSsg|] \}}t||qSr2) _parent_pathr r2r2r3 :sz"_simple_layout..c3s6|]\}}ttg|dRt|kVqdSrdN)_normalize_pathrsplit)rkeyvalue)rnr2r3r;s  z!_simple_layout..)rrJrM commonpathrall)rrLrClayoutr2)rLrnrCr3rs  rcCs0||r|dt| n|}|dtjS)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)rblenrstriprJr)r<pkg_pathrnr2r2r3r=As r=rGccs~t|jpgEdH|jpg}dd|D}|jr|jVn|jp#g}|dd|D7}|D] }|d\}}}|Vq/dS)NcSsg|]}d|vr|qSrdr2rmodr2r2r3r>Ssz"_find_packages..cSsg|] }d|jvr|jqSrJrurxr2r2r3r>Xsrd)iterr py_modules ext_package ext_modules rpartition)rGrQnested_modulesrSmodulepackage_r2r2r3rOs   rccsL|jpg}dd|DEdH|js$|jpg}dd|DEdHdSdS)Ncss|] }d|vr|VqdSr?r2rKr2r2r3rarz*_find_top_level_modules..css |] }d|jvr|jVqdSr?rMrNr2r2r3res)rQrRrS)rGrQrSr2r2r3r!_s  r!rIcs fddt|D}t|S)Ncsi|] }|tt|qSr2)_absolute_rootrr;rLrIr2r3rmsz'_find_package_roots..)sorted_remove_nested)rrLrI pkg_rootsr2rZr3r"hs r"rMcCs4t|}|j}|rt|St||jS)z(Works for packages and top-level modules)rrnrcr;rgru)rMpath_rnr2r2r3rYus  rYr]ccsv|D]5}d|vr q|d}tt|dddD]}d|d|}tt||d}|r4||vr7|VqqdS)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. rdrNr?)rArangerGrNrrrc)r]r<partsi partial_namerMr2r2r3r%s  r%ccsB|D]}t||d}t|rt|ds||gfVqdS)Nr?z __init__.py)rrrc)rr]r<rMr2r2r3r$s  r$csPt|}tt|D]\tfdd|Dr%|q|S)Nc3s*|]\}}|kot||VqdSr@) _is_nested)rother other_pathrMr<r2r3rs  z!_remove_nested..)r#copyreversedrranyr)r]rr2rhr3r\s  r\r<rIrn parent_pathcCsDt|}||dddd}||o!|tt|g|RkS)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 r?r_rd)r@rstriprA startswithr)r<rIrnrl norm_pkg_pathrestr2r2r3res  refilenamecCs6tjdkr tj|n|}tjtjtj|S)z1Normalize a file/dir name for comparison purposescygwin)sysplatformrJrMabspathnormcaserealpathnormpath)rqrr2r2r3r@sr@dir_cCstj|ddt||S)zFCreate a directory ensured to be empty. Existing files may be removed.T) ignore_errors)rrmtreerJmakedirs)ryr2r2r3rs rrucCstdd|}|s J|S)zMake a string safe to be used as Python identifier. >>> _make_identifier("12abc") '_12abc' >>> _make_identifier("__editable__.myns.pkg-78.9.3_local") '__editable___myns_pkg_78_9_3_local' z \W|^(?=\d)rX)resub isidentifier)rusafer2r2r3r&s r&c@s$eZdZddZddZddZdS)rhcCs(||_||_||_||_g|_d|_dS)NF)rHrIrj editable_namerdry_run)rErHrjrrIr2r2r3rs  z_NamespaceInstaller.__init__cCstj|j|jS)zInstallation target.)rJrMrNrjrrDr2r2r3 _get_targetsz_NamespaceInstaller._get_targetcCstt|jS)z1Where the modules/packages should be loaded from.)reprr;rIrDr2r2r3 _get_rootsz_NamespaceInstaller._get_rootN)r5r6r7rrrr2r2r2r3rhs rha< import sys from importlib.machinery import ModuleSpec 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): for pkg, pkg_path in reversed(list(MAPPING.items())): if fullname == pkg or fullname.startswith(f"{{pkg}}."): rest = fullname.replace(pkg, "", 1).strip(".").split(".") return cls._find_spec(fullname, Path(pkg_path, *rest)) 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 rrcCs(tt|ddd}tj|||dS)z_Create a string containing the code for the``MetaPathFinder`` and ``PathEntryFinder``. cSs|dS)Nrr2)rr2r2r3?sz"_finder_template..)rBrurr)r#r[r_FINDER_TEMPLATEformatrr2r2r3r'9sr'c@eZdZdZdS)rzCurrently there is no clear way of displaying messages to the users that use the setuptools backend directly via ``pip``. The only thing that might work is a warning, although it is not the most appropriate tool for the job... Nr5r6r7r8r2r2r2r3rCrc@r)r8zCFile system does not seem to support either symlinks or hard links.Nrr2r2r2r3r8Krr8)Wr8loggingrJr}rrsrYr- contextlibrenumrinspectr itertoolsrpathlibrtempfilertypingrr r r r r rrrr setuptoolsrrrrsetuptools.command.build_pyrrsetuptools.discoveryrsetuptools.distrrr version_infortyping_extensionsabcrr;rr getLoggerr5rr"rrr<rrrrboolrrr=rr!r"rYr%r$r\rer@rr& Installerrhrr' UserWarningr FileErrorr8r2r2r2r3s       0         $  G%  ,        "   H