-ϘQ
d Z ddlZddlZddlZddlZddlZddlZddlmZ ddl m
Z
ddl m Z ddl
mZ ddlmZ ddlmZ dd lmZmZmZmZmZmZmZmZm Z m Z d
d l m Z m 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/ ej0 dk rddlm1Z1 nerddl2m1Z1 nddl3m4Z1 e e5ef Z6 e de6 Z7 ej8 e9 Z: G d de
Z;dZ G d d e1 Z? G d d Z@ G d! d"e@ ZA G d# d$ ZBd%e5d&eCfd'ZDd(ed&eEfd)ZFd*ee5 d+ee5e5f d,ed&eEfd-ZGd. ZHd/e'd&ee5 fd0ZId/e'd&ee5 fd1ZJd*ee5 d+ee5e5f d2e6d&ee5e5f fd3ZKd4e6d&e5fd5ZLd6ee5e5f d&ee5 fd7ZMd*ee5 d6ee5e5f d&eee5ee5 f fd8ZNd6ee5e5f d&ee5e5f fd9ZOd:e5d;e5dZPd?e7d&e7fd@ZQ G dA dBe#jR ZSdCZTdDe5dEee5e5f dFee5ee5 f d&e5fdGZU G dH dIe"jV ZW G dJ dKe+ ZXdS )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
namespacesfind_package_path) Distribution)InformationOnly SetuptoolsDeprecationWarningSetuptoolsWarning )build_py WheelFile) )Protocol)ABC_P)boundc J e Zd ZdZdZdZdZedee dd fd Z
dS )
_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 |s t j S | }|t j vrt j d|d |dk rt
j ddd t | 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 OptionErrorr emit)clsr. _modes /builddir/build/BUILD/imunify360-venv-2.6.2/opt/imunify360/venv/lib/python3.11/site-packages/setuptools/command/editable_wheel.pyconvertz_EditableMode.convertQ s ) ( (
1 1 1$%Wt%W%W%WXX X H ( -* ;
U## N) __name__
__module__ __qualname____doc__STRICTr4 r1 classmethodr strr< r= r; r* r* E s_ 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.
c V e Zd ZdZdZdddd eej pd fgZd Zd Z d
Z
d Z d Z d
e
e fdZdedededefdZd Zd
eee eeef f fdZdedededed
eee eeef f f
dZd ZdefdZd Zd efd Zded eded
d fd Z dS )!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=N c > d | _ d | _ d | _ d | _ d S N)dist_dir
dist_info_dir project_dirr. selfs r; initialize_optionsz!editable_wheel.initialize_options s$
! r= c | j }|j p t j | _ |j pi | _ t
| j p$t j | j d | _ d S )Ndist)
distributionsrc_rootoscurdirrO package_dirr rM pathjoin)rQ rT s r; finalize_optionsz editable_wheel.finalize_options sX =5BI +1r T] Tbgll4;KV.T.TUU
r= c | j d | | d | d }| | j | | d S # t $ rU t j
| j j p| j
}t | w xY w)NT)exist_ok bdist_wheel)project)rM mkdir_ensure_dist_inforeinitialize_commandget_finalized_commandwrite_wheelfilerN _create_wheel_file Exception traceback print_excrU nameget_name_DebuggingTipsr8 )rQ r_ r` s r; runzeditable_wheel.run s M . . . " " $ $ $
% %m 4 4 4 44]CCK ' '(: ; ; ; # #K 0 0 0 0 0 ! ! !',L0A0J0J0L0LG 0 0 0 s
BB A C+c f | j W| d }| j |_ | | |j | _ d S t
| j d sJ t | j d sJ d S )N dist_infoz
.dist-infoMETADATA)
rN rc rM
output_dirensure_finalizedrm rD endswithr exists)rQ ro s r; rb z editable_wheel._ensure_dist_info s % 11+>>I#'=I & & ( ( ( MMOOO!*!8D t)**33LAA A AA*J77>>@@ @ @@ @ @r= c | j }|j sd S t | j | j dd }t |||| }| d S )NrJ .) rU namespace_packagesr rO rY getresolve_NamespaceInstallerinstall_namespaces)rQ installation_dir
pth_prefixrT rV installers r; _install_namespacesz"editable_wheel._install_namespaces sw & F($*:*>*>r3*G*GHHPPRR'.>
HUU $$&&&&&r= r/ c | j rt | j j n
t }t t | d }t
|d S )Nz
*.egg-info)rN r parentmaprD globnext)rQ
parent_dir
candidatess r; _find_egg_info_dirz!editable_wheel._find_egg_info_dir sT 8<8JVT$,--44PTPVPV
jool ; ;<<
J%%%r= rj unpacked_wheel build_libtmp_dirc | j }t | }t | }t t || dd }t t || dd }t t || dd } | dd }
t | |
_ d|
_ | dd } | d d } |x| _ x| _ | _ |x| _ x| _
| _ | x| _ | _
|| _ || _ | d
}
d|
_ t | | _ | d }d |_ | |_ | | | d
S )a Configure 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_scriptsr FN)rU rD r rc egg_baseignore_egg_info_in_manifest
build_platlib
build_purelibr install_purelibinstall_platlib install_libr
build_scriptsinstall_headers install_dataget_command_objno_ep
build_tempcompiler existing_egg_info_dir_set_editable_moderr )rQ rj r r r rT wheelr r r r r r r r s r; _configure_buildz editable_wheel._configure_build s N## NN 44??@@d>d>>>9EEFFd>d>>>9EEFF ,,ZD,QQ LL/3,))'d)KK++I$+OOFOOOe 1EORWW W'"9G>>g~ r= dist_namec | |||| | | \ }}| d | d | d ||fS )Nr r r )r _run_build_subcommandsr _run_install)rQ r r r r r r s r; _run_build_commandsz"editable_wheel._run_build_commands s
i GLLL ##%%% 4466w )$$$ )$$$ &!!!g~ r= c | d }| D ]`}| | }|dk r.t | t k r| | K| | adS )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 r N)rd r type build_py_cls _safely_run run_command)rQ r rj r s r; r z%editable_wheel._run_build_subcommands s 33G<<**,, ' 'D,,T22Cz!!d3ii<&?&? &&&& &&&& ' 'r= r c | | S # t $ r4 t j ddt j d| d| d Y d S w xY w)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.
)r rg r r8 rh
format_exc)rQ r s r; r zeditable_wheel._safely_run) s ##H-- - ( -B%'' 9A .6
s :AAc
ddl m} | d }|j }d | }d}| d| d| d}t
| j | }| r| t | } t d }
t d } | 5 } |
5 }
| 5 }t
| t
| j j }t j
| j | | | | | || |
| \ }}| |||
}|5 ||d
5 } |||| | | d d d n # 1 swxY w Y d d d n # 1 swxY w Y d d d n # 1 swxY w Y d d d n # 1 swxY w Y d d d n # 1 swxY w Y |S ) Nr r! ro -z
0.editablez.whl)suffixz
.build-libz .build-tempw)wheel.wheelfiler" rd rj r[ get_tagr rM rt unlinkr rN shutilcopytreer r _select_strategy write_files)rQ r_ r" ro r tag build_tag archive_name
wheel_pathr r build_tmpunpackedlibtmpunpacked_dist_infor r strategy wheel_objs r; rf z!editable_wheel._create_wheel_fileE sH ------..{;; N hh{**,,-- #;;i;;#;;; $- 66
+<@@@&l;;; &m<<<
0x 0c9 0!%hT5G0H0H0M!N!N OD .0B C C C $ $Xy 9 9 9 ! 5 5i3PS T TNE7,,YSAAH
0
099Z55
0E7333%%h///
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 s G0 G B G
F+ %#F F+ FF+ F F+ G+F/
/G2F/
3G6 GG G G
G
G0G G0 G !G00G47G4categoryc t | j d| d }|rB | r:t d| d | d| d S d S d S )Nhas_z Installing z as non editableinstall_)getattrrU _loggerinfor )rQ r has_categorys r; r zeditable_wheel._run_installa s t 02C2C2CTJJ 4LLNN 4 LLAxAAA B B B 2 2 2 3 3 3 3 3 4 4 4 4r= r EditableStrategyc \ d| d| }t | j }t | j }|t j u r:t
t | j d| }t | j ||| S t | j }t || j | } |t j u }
t | j dhk r| s|
r@| j dd } t | j |t || g S t! | j | S )zDDecides which strategy to use to implement an editable installation.
__editable__.r r rJ rv )r rO r* r< r. rB
_empty_dir _LinkTreerU _find_packages_simple_layoutrY r1 setrx
_StaticPth_TopLevelFinder) rQ rj r r
build_namerO r.
auxiliary_dirpackageshas_simple_layoutis_compat_modesrc_dirs r; r z editable_wheel._select_strategyg s# 2T11C11
4+,, $$TY// =' ' ' &tD, (. (&**2s33G d /['8R8R7STT T t 0$777r= ) r> r? r@ rA descriptionr r* user_optionsrR r\ rm rb r r rD r _Pathr r r r
r
r r r r rf r r rE r= r; rG rG x s
WK LK $ !6!<"==>L V V V " A A A' ' '&HSM & & & &
0#0#).0#;@0#KP0# 0# 0# 0#d # # # d3ic3h .G(H .3 @E PU tCy$sCx.( ) ' ' ',C 8 84S 4 4 4 4 88 8 8
8 8 8 8 8 8r= rG c J e Zd Zdddee deeef fdZd Zd ZdS ) r r r" r r c d S rL rE )rQ r r r s r; __call__zEditableStrategy.__call__ r= c d S rL rE rP s r; __enter__zEditableStrategy.__enter__ r r= c d S rL rE rQ _exc_type
_exc_value
_tracebacks r; __exit__zEditableStrategy.__exit__ r r= N) r> r? r@ r
rD r
r r r rE r= r; r r sh k $s) d3PS8n r= r c j e Zd Zdededee fdZdddee deeef fd Z d
Z
d Z d S )
r rT rj path_entriesc 0 || _ || _ || _ d S rL )rT rj r )rQ rT rj r s r; __init__z_StaticPth.__init__ s (r= r r" r r c d d | j D }t | d }| d| j d| d S )N
c 3 X K | ]%}t | V &d S rL )rD ry ).0ps r; z&_StaticPth.__call__.. s2 I I!S - - I I I I I Ir= r .pth)r[ r _encode_pthwritestrrj )rQ r r r entriescontentss r; r z_StaticPth.__call__ s` )) I It7H I I IJJ '~~~..
6ty666AAAAAr= c dt t t j | j d}t
|t z | S )Nz_
Editable install will be performed using .pth file to extend `sys.path` with:
z
)listr rW fspathr r warning_LENIENT_WARNINGrQ msgs r; r z_StaticPth.__enter__ sQ
c")T .// 0 0 ../// r= c d S rL rE r s r; r z_StaticPth.__exit__ r r= N) r> r? r@ r rD r
r r r
r r r rE r= r; r r s )\ ) )DJ ) ) ) )
Bk B$s) Bd3PS8n B B B B
r= r c e Zd ZdZdedededef fd Zddd ee d
e eef f fd Z
d ed
e e fdZ ddedefdZ
d Zd Zd Z xZS )r a`
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.
rT rj r r c t | | _ t | | _ | d j | _ t ||| j g d S )Nr ) r r ry r r copy_file_filesuperr )rQ rT rj r r __class__s r; r z_LinkTree.__init__ sn "- 0 0 i 0022))*55?
td&8%9:::::r= r r" r r c z | || t ||| d S rL )
_create_linksr r )rQ r r r r s r; r z_LinkTree.__call__ s; 5'***
w/////r= filer/ c * t t 5 t | | j }t
| t j d cd d d S # 1 swxY w Y d S )N/)
r
ValueErrorr ry relative_tor rD replacerW sep)rQ r rZ s r; _normalize_outputz_LinkTree._normalize_output s
j
!
! 2 2::%%''33DNCCDt99$$RVS11 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 ts A&BB B Nrelative_outputsrc_filec | j |z }|j s|j d | ||| d S )NT)parentslink)r r is_dirra r )rQ r% r& r* dests r; _create_filez_LinkTree._create_file s\ !O3{!!## , K d + + +
8T
-----r= c j dd t j rdnd} fd| D }| d d |D ]3} | }|r||vr || 4| D ] \ }} ||| d S )NT)r( r^ symhardc B i | ]\ }} | | S rE )r$ )r kvrQ s r;
z+_LinkTree._create_links.. s- TTTTQD**1--qTTTr= r) )r ra _can_symlink_filesitemspopr$ r- )rQ outputsoutput_mapping link_typemappingsoutputrelativesrcs ` r; r z_LinkTree._create_links s === /0B C COEE TTTT^=Q=Q=S=STTT T4 4 4F--f55H
4HH 4 4!!(F333 %^^ - - = =MHc h) < < < < = =r= c N d}t |t z | S )Nz=Strict editable install will be performed using a link tree.
)r r _STRICT_WARNINGr s r; r z_LinkTree.__enter__ s# No-... r= c F d| j d}t j d| d S )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.)r r r8 rQ r r r r s r; r z_LinkTree.__exit__ s:
5s;;;;;r= rL )r> r? r@ rA r rD r r r
r
r r r$ r- r r r
__classcell__)r s @r; r r s'
;
;
;
;
;
;
;
;
;
;0k 0$s) 0d3PS8n 0 0 0 0 0 0c hsm . .C .3 . . . . = = =
< < < < < < . s& DDb"bDDDDDDr= c L i | ] }|t |j j pd !S )rJ )r rT rV )r pkgrootsrQ s r; r4 z,_TopLevelFinder.__call__.. sB
"3ty/A/GRHH
r= r z.finderutf-8z.pyzimport z; z
.install()r )rT rV rW rX r r _find_top_level_modulesrY _find_package_rootsdict_find_namespacesr _find_virtual_namespacesrw rj r safe_identifierbytes_finder_templater
r )
rQ r r r rV top_levelrY namespaces_legacy_namespacesrj findercontentrL s
` @r; r z_TopLevelFinder.__call__ s 9%2.335LTY5W5WXX i+1r #I{HEE,0 !3!9r5AADD$ r? r@ r rD r r
r
r r r rE r= r; r r s \ Ak A$s) Ad3PS8n A A A A>
< < < < >> _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
c 4 i | ]}|t | S rE r )r rK rY rO s r; r4 z"_simple_layout..` s(
X
X
Xc$S+{CC
X
X
Xr= rJ c 4 g | ]\ }}t || S rE ) _parent_path)r r2 r3 s r;
z"_simple_layout..c s& O O O1 a!3!3 O O Or= c 3 K | ]:\ }}t j t g| d R | V ;dS rv N)r same_pathr split)r keyvaluer s r; r z!_simple_layout..d sa C V5ciinn555u== r= )r rW rZ
commonpathr6 all)r rY rO layoutr s `` @r; r r A s > Y
X
X
X
Xx
X
X
XF .; B:--
W
O O O O O
P
PF ,,.. r= c | | r|dt | n|}| dt j z S )a7 Infer 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 )rs lenrstriprW r# )rK pkg_pathr s r; r~ r~ j sJ '/&7&7&<&<
JXkS k
"
"(F ==rv & &&r= rT c # K t | j pg E d {V | j pg }d |D }| j r
| j V n| j pg }|d |D z
}|D ] }| d \ }}}|V d S )Nc g | ]}d |v | S rv rE r mods r; r z"_find_packages..| s >>>c3#::c:::r= c . g | ]}d |j v |j S r rj r xs r; r z"_find_packages.. s! HHHa#--16---r= rv )iterr
py_modules ext_package ext_modules
rpartition)rT r nested_modulesr modulepackage_s r; r r x s DM'R((((((((( &BJ>>Z>>>N I &," HH;HHHH ))#..
A
r= c # K | j pg }d |D E d {V | j s | j pg }d |D E d {V d S d S )Nc 3 " K | ]
}d |v|V dS r rE r s r; r z*_find_top_level_modules.. s& <<S^^^^^^<. s0 EEq3af3D3DAF3D3D3D3DEEr= )r r r )rT r r s r; rN rN s &BJ<. s@ ! ! ! ^ -c; I I
J
J! ! !r= )sorted_remove_nested)r rY rV pkg_rootss `` r; rO rO sI
! ! ! ! !(##! ! !I
) $ $$r= rZ c t | }|j }| r!t | S t | |j z S )z(Works for packages and top-level modules)r r rt rD ry rj )rZ path_r s r; r r sY JJE
\F ||~~ 25==??###6>>##ej0111r= r c # > K | D ]}d|vr| d }t t | dz
dd D ]Y}d |d| }t t || d }| r|| vr|V ZdS )a8 By 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.
rv r r NrJ )r ranger r[ r r rt )r rK partsi partial_namerZ s r; rR rR s # # c>> #s5zzA~q"-- # #A 88E"1"I..L), 2FFGGD;;==
#L $A$A"""" # # #r= c # K | D ]]}t ||d }t | r)t |d s||gfV ^d S )NrJ z __init__.py)r r rt )r r rK rZ s r; rQ rQ s| i44 :: tD-'@'@'G'G'I'I - r= c : t | }t t | D ]H\ t fd| D r| I|S )Nc 3 N K | ] \ }}|k ot || V d S rL )
_is_nested)r other
other_pathrZ rK s r; r z!_remove_nested.. sR
!z
5L EZT5* E E
r= )rP copyreversedr r6 anyr7 )r r< rZ rK s @@r; r r s
)..""
#
#F d9??#4#4 5 566 T
%.__%6%6
JJsOOO Mr= rK r r parent_pathc t j | }| |dd d d }| | o"|t j t
|g|R 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
rJ r rv )r normpathr" stripr
startswithr )rK r r r
norm_pkg_pathrests r; r r s N8,,M ;;vr1 % % + +C 0 0 6 6s ; ;D >>& ! ! mu~ [ 4 8 8 ' r= dir_c Z t j | d t j | | S )zFCreate a directory ensured to be empty. Existing files may be removed.T)
ignore_errors)r rmtreerW makedirs)r s r; r r s,
M$d++++K Kr= c e Zd Zd Zd Zd ZdS )rz c Z || _ || _ || _ || _ g | _ d| _ d S )NF)rU rV r|
editable_namer8 dry_run)rQ rU r| r rV s r; r z _NamespaceInstaller.__init__ s3 (
0 * r= c f t j | j | j | j z S )zInstallation target.)rW rZ r[ r| r nspkg_extrP s r; _get_nspkg_filez#_NamespaceInstaller._get_nspkg_file s% w||D 143E3VWWWr= c D t t | j S )z1Where the modules/packages should be loaded from.)reprrD rV rP s r; _get_rootz _NamespaceInstaller._get_root s C
&&'''r= N)r> r? r@ r r r rE r= r; rz rz sD X X X( ( ( ( (r= rz a 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):
extra_path = []
# 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], *extra_path])
# 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
rj r r c t t | d }t | || S )z_Create a string containing the code for the``MetaPathFinder`` and
``PathEntryFinder``.
c | d S )Nr rE )r s r; z"_finder_template.._ s
1 r= )r rj r r )rP r r6 _FINDER_TEMPLATEformatr s r; rU rU Y sC 6'--//~~>>>??G " "g* " U UUr= c e Zd ZdZdS )rw zCFile system does not seem to support either symlinks or hard links.N)r> r? r@ rA rE r= r; rw rw c s MMMMr= rw c e Zd ZdZdZdZdS )rl z!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
r2 N)r> r? r@ _SUMMARY_DETAILS _SEE_DOCSrE r= r; rl rl g s! 2HH* 2IIIr= rl )YrA loggingrb rW r r` rh
contextlibr enumr inspectr itertoolsr pathlibr tempfiler typingr r
r r r
r r r r r rJ r r r r r discoveryr rT r warningsr r r r r r r" ra r% typing_extensionsabcr& rD r r' getLoggerr> r r* r@ r rG r r r r rT r boolr5 r r~ r rN rO r rR rQ r r r Installerrz r rU FileErrorrw rl rE r= r; r s
' ' ' ' ' ' * ) ) ) ) )
/ . . . . . *))))))v $*******######
c4i WT
'
H
%
%&$ &$ &$ &$ &$D &$ &$ &$R G8 G8 G8 G8 G8W G8 G8 G8T x .C< C< C< C< C<
C< C< C