o JAf| @sdZddlZddlZddlZddlZddlZddlZddlmZddl m Z ddl m Z ddl mZddlmZddlmZdd lmZmZmZmZmZmZmZmZmZmZd d lmZm Z m!Z!m"Z"m#Z#m$Z$d d l%m&Z&d d l'm(Z(ddl)m)Z*erddl+m,Z,ej-dkrddlm.Z.nerddl/m.Z.nddl0m1Z.ee2efZ3ede3dZ4e5e6Z7Gddde Z8dZ9dZ:GdddeZ;Gddde.ZGd"d#d#Z?d$ed%e@fd&d'ZAd(ee2d)ee2e2fd*ed%e@fd+d,ZBd-d.ZCd/e(d%ee2fd0d1ZDd/e(d%ee2fd2d3ZEd(ee2d)ee2e2fd4e3d%ee2e2ffd5d6ZFd7e3d%e2fd8d9ZGd:ee2e2fd%ee2fd;d<ZHd(ee2d:ee2e2fd%eee2ee2ffd=d>ZId:ee2e2fd%ee2e2ffd?d@ZJdAe2dBe2dCe2dDe2d%e@f dEdFZKdGe4d%e4fdHdIZLGdJdKdKe$jMZNdLZOdMe2dNee2e2fdOee2ee2fd%e2fdPdQZPGdRdSdSeQZRGdTdUdUe#jSZTGdVdWdWeRZUdS)Xa 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)CommandSetuptoolsDeprecationWarning_normalization_patherrors namespacesfind_package_path) Distribution)build_py 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). strictZlenientcompatmodereturncCsN|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)_modemsgr5c/usr/lib/python3.10/site-packages/setuptools-67.5.1-py3.10.egg/setuptools/command/editable_wheel.pyconvertMs  z_EditableMode.convertN) __name__ __module__ __qualname____doc__STRICTr,r+ classmethodrstrr7r5r5r5r6r&Asr&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_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=NcCsd|_d|_d|_d|_dSN)dist_dir dist_info_dir project_dirr)selfr5r5r6initialize_options}s z!editable_wheel.initialize_optionscCs@|j}|jptj|_|jpi|_t|jptj |jd|_dS)Ndist) distributionsrc_rootoscurdirrF package_dirrrDpathjoin)rHrJr5r5r6finalize_optionss  zeditable_wheel.finalize_optionscCs|z#|jjdd||d|d}||j||WdSty=t |j j p6|j }t|w)NT)exist_ok bdist_wheel)rDmkdir_ensure_dist_inforeinitialize_commandget_finalized_commandZwrite_wheelfilerE_create_wheel_file Exception traceback print_excrKnameget_name_DebuggingTipsr1)rHrTprojectr5r5r6runs     zeditable_wheel.runcCsd|jdur|d}|j|_|||j|_dSt|jds&Jt|jd s0JdS)N dist_infoz .dist-infoMETADATA) rErWrD output_dirensure_finalizedrar>endswithrexists)rHrbr5r5r6rVs   z editable_wheel._ensure_dist_infocCsD|j}|jsdSt|j|jdd}t||||}|dS)NrB.) rKnamespace_packagesrrFrOgetresolve_NamespaceInstallerZinstall_namespaces)rHinstallation_dirZ pth_prefixrJrL installerr5r5r6_install_namespacess  z"editable_wheel._install_namespacesr*cCs2|jr t|jjnt}tt|d}t|dS)Nz *.egg-info)rErparentmapr>globnext)rH parent_dir candidatesr5r5r6_find_egg_info_dirs z!editable_wheel._find_egg_info_dirr]unpacked_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)rKr>rrWegg_baseignore_egg_info_in_manifest build_platlib build_purelibrxinstall_purelibinstall_platlib install_libr build_scriptsinstall_headers install_dataget_command_objno_ep build_tempcompilervexisting_egg_info_dir_set_editable_modere)rHr]rwrxryrJwheelrzr{r|r}rrrrr5r5r6_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)rKrget_sub_commandshasattrrr)rHrJrcmd_namecmdr5r5r6rs     z!editable_wheel._set_editable_modecCsjg}i}|d}|D]#}||}t|dr"||p gt|dr0||p.iq ||fS)Nr get_outputsget_output_mapping)rXrrextendrupdater)rHfilesmappingrrrr5r5r6_collect_build_outputss     z%editable_wheel._collect_build_outputs dist_namecCsJ|||||||\}}|d|d|d||fS)Nr{r|rz)r_run_build_subcommandsr _run_install)rHrrwrxryrrr5r5r6_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. rrN)rXrtype build_py_cls _safely_run run_command)rHrr]rr5r5r6r 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. r stacklevel)rrZr[ format_excr0r1r)rHrr4r5r5r6r 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) Nrrrb-z 0.editablez.whl)suffixz .build-libz .build-tempw)wheel.wheelfilerrXr]rQZget_tagrrDrgunlinkrrEshutilcopytreeror_select_strategyZ write_files)rHrTrrbrtagZ build_tag archive_name wheel_pathrwrxZ build_tmpZunpackedlibtmpZunpacked_dist_inforrZstrategyZ wheel_objr5r5r6rY4sB        (   z!editable_wheel._create_wheel_filecategorycCsLt|jd|d}|r"|r$td|d|d|dSdSdS)NZhas_z Installing z as non editableinstall_)getattrrK_loggerinfor)rHrZ has_categoryr5r5r6rPs  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__.rrrBrh)rrFr&r7r)r< _empty_dir _LinkTreerK_find_packages_simple_layoutrOr+setrj _StaticPth_TopLevelFinder) rHr]rrxZ build_namerFr) auxiliary_dirpackagesZhas_simple_layoutZis_compat_modesrc_dirr5r5r6rVs      zeditable_wheel._select_strategy)r8r9r:r; descriptionrr& user_optionsrIrRrarVrorr>rv_Pathrrrr r rrrrrYrrr5r5r5r6r?os`   2"   r?c@s>eZdZdddeedeeeffddZddZd d Zd S) rrrrrcCdSrCr5rHrrrr5r5r6__call__rzEditableStrategy.__call__cCrrCr5rGr5r5r6 __enter__urzEditableStrategy.__enter__cCrrCr5rH _exc_type _exc_value _tracebackr5r5r6__exit__xrzEditableStrategy.__exit__N) r8r9r:r r>r rrrr5r5r5r6rqs" rc@sXeZdZdededeefddZdddeed eeeffd d Z d d Z ddZ dS)rrJr] path_entriescCs||_||_||_dSrC)rJr]r)rHrJr]rr5r5r6__init__}s z_StaticPth.__init__rrrrcCs@ddd|jD}t|dd}|d|jd|dS)N css|] }t|VqdSrC)r>rk).0pr5r5r6 z&_StaticPth.__call__..utf-8r.pth)rQrbyteswritestrr])rHrrrentriescontentsr5r5r6rsz_StaticPth.__call__cCs,dtttj|jd}t|t|S)Nz_ Editable install will be performed using .pth file to extend `sys.path` with: z )listrqrMfspathrrwarning_LENIENT_WARNINGrHr4r5r5r6rs z_StaticPth.__enter__cCrrCr5rr5r5r6rrz_StaticPth.__exit__N) r8r9r:rr>r rrr rrrr5r5r5r6r|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. rJr]rrxcs>t||_t||_|dj|_t|||jgdS)Nr) rrrkrxr copy_file_filesuperr)rHrJr]rrx __class__r5r6rs z_LinkTree.__init__rrrrcs |||t|||dSrC) _create_linksrrrrr5r6rs z_LinkTree.__call__filer*cCsRttt||j}t|tj dWdS1s"wYdS)N/) r ValueErrorrrk relative_torxr>replacerMsep)rHrrPr5r5r6_normalize_outputs  z_LinkTree._normalize_outputNrelative_outputsrc_filecCs6|j|}|js|jjdd|j|||ddS)NT)parentslink)rrpis_dirrUr)rHrrrdestr5r5r6 _create_files  z_LinkTree._create_filecsjjdddtjrdnd}fdd|D}|dd|D]}|}|r7||vr7||q$|D] \}}j|||dqs z+_LinkTree._create_links..r)rrU_can_symlink_filesitemspoprr)rHoutputsZoutput_mappingZ link_typeZmappingsoutputZrelativesrcr5rGr6rs     z_LinkTree._create_linkscCd}t|t|S)Nz=Strict editable install will be performed using a link tree. )rr_STRICT_WARNINGrr5r5r6rz_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. )rr0r1InformationOnlyrHrrrr4r5r5r6rsz_LinkTree.__exit__rC)r8r9r:r;rr>rrr r rrrrrrr __classcell__r5r5rr6rs" & rc@sPeZdZdedefddZdddeedeeeffd d Zd d Z d dZ dS)rrJr]cCs||_||_dSrC)rJr])rHrJr]r5r5r6rs 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|]}|gfVqdSrCr5)rnsr5r5r6rsz+_TopLevelFinder.__call__..rz.finderrz.pyzimport z; z .install()r)rJrLrMrNrr_find_top_level_modulesrO_find_package_rootsdict_find_namespacesr_find_virtual_namespacesr]rsafe_identifierr_finder_templater) rHrrrrL top_levelrOrootsZ namespaces_r]findercontentr5r5r6rs   z_TopLevelFinder.__call__cCr )Nz=Editable install will be performed using a meta path finder. )rrrrr5r5r6rr z_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. )r0r1r rr5r5r6rsz_TopLevelFinder.__exit__N) r8r9r:rr>rr r rrrr5r5r5r6rs " 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.txtZfile1r)encodingTzFile system does not seem to support either symlinks or hard links. Strict editable installs require one of them to be supported.F)rr>rkr write_textrAttributeErrorNotImplementedErrorOSErrorrMsymlink is_symlink read_textrrZLinksNotSupported)rrZpath1path2exr4r5r5r6rs*   $rrrOrFcs^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|qSr5rrpkg)rOrFr5r6r2s z"_simple_layout..rBcSsg|] \}}t||qSr5) _parent_pathrr5r5r6 8sz"_simple_layout..c3s2|]\}}ttg|dR|VqdSrhN)r same_pathrsplit)rkeyvalue)rpr5r6r9s  z!_simple_layout..)rrMrP commonpathrall)rrOrFZlayoutr5)rOrprFr6rs  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)rflenrstriprMr)r*pkg_pathrpr5r5r6r+?s r+rJccs~t|jpgEdH|jpg}dd|D}|jr|jVn|jp#g}|dd|D7}|D] }|d\}}}|Vq/dS)NcSsg|]}d|vr|qSrhr5rmodr5r5r6r,Qsz"_find_packages..cSsg|] }d|jvr|jqSr7r]rxr5r5r6r,Vsrh)iterr py_modules ext_package ext_modules rpartition)rJr>Znested_modulesr@modulepackage_r5r5r6rMs   rccsL|jpg}dd|DEdH|js$|jpg}dd|DEdHdSdS)Ncss|] }d|vr|VqdSr-r5r8r5r5r6r_rz*_find_top_level_modules..css |] }d|jvr|jVqdSr-r:r;r5r5r6rcs)r>r?r@)rJr>r@r5r5r6r]s  rrLcs fddt|D}t|S)Ncsi|] }|tt|qSr5)_absolute_rootrr)rOrLr5r6rksz'_find_package_roots..)sorted_remove_nested)rrOrL pkg_rootsr5rFr6rfs rrPcCs4t|}|j}|rt|St||jS)z(Works for packages and top-level modules)rrprgr>rkr])rPZpath_rpr5r5r6rEss  rErIccsv|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. rhrrNrB)r/ranger4rQrrrg)rIr*partsi partial_namerPr5r5r6r~s  rccsB|D]}t||d}t|rt|ds||gfVqdS)NrBz __init__.py)rrrg)rrIr*rPr5r5r6rs  rcsPt|}tt|D]\tfdd|Dr%|q|S)Nc3s*|]\}}|kot||VqdSrC) _is_nested)rother other_pathrPr*r5r6rs  z!_remove_nested..)rcopyreversedrranyr)rIrr5rRr6rHs  rHr*r6rp parent_pathcCsHt|}||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 rBrrh)rnormpathrstripr/ startswithr)r*r6rprVZ norm_pkg_pathrestr5r5r6rOs  rOdir_cCstj|ddt||S)zFCreate a directory ensured to be empty. Existing files may be removed.T) ignore_errors)rrmtreerMmakedirs)r[r5r5r6rs rc@s$eZdZddZddZddZdS)rlcCs(||_||_||_||_g|_d|_dS)NF)rKrLrm editable_namerdry_run)rHrKrmr_rLr5r5r6rs  z_NamespaceInstaller.__init__cCstj|j|jS)zInstallation target.)rMrPrQrmr_rGr5r5r6 _get_targetsz_NamespaceInstaller._get_targetcCstt|jS)z1Where the modules/packages should be loaded from.)reprr>rLrGr5r5r6 _get_rootsz_NamespaceInstaller._get_rootN)r8r9r:rrarcr5r5r5r6rls rla< 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 r]rrcCs(tt|ddd}tj|||dS)z_Create a string containing the code for the``MetaPathFinder`` and ``PathEntryFinder``. cSs|dS)Nrr5)rr5r5r6*sz"_finder_template..)r0r]rr)rrGr_FINDER_TEMPLATEformatrer5r5r6r$src@eZdZdZdS)r zCurrently 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... Nr8r9r:r;r5r5r5r6r .r c@rh)r&zCFile system does not seem to support either symlinks or hard links.Nrir5r5r5r6r&6rjr&c@seZdZedefddZdS)r_r`cCs d|d}tj||dddS)Nz#An error happened while installing aX in editable mode. ************************************************************************ The following steps are recommended to help debugging this problem: - Try to install the project normally, without using the editable mode. Does the error still persists? (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 persist 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 More information about editable installs can be found in the docs: https://setuptools.pypa.io/en/latest/userguide/development_mode.html ************************************************************************ rr)r0r1)r2r`r4r5r5r6r1;s z_DebuggingTips.warnN)r8r9r:r=r>r1r5r5r5r6r_:sr_)Vr;loggingrMrsysr[r0 contextlibrenumrinspectr itertoolsrpathlibrtempfilertypingrr r r r r rrrrrBrrrrrr discoveryrrJrrrrr version_infor"typing_extensionsabcr#r>rr$ getLoggerr8rr&r rr?rrrrboolrrr+rrrrErrrHrOr Installerrlrfr UserWarningr  FileErrorr&r_r5r5r5r6s       0         $ G%  ,        "  H