~
d Z ddlZddlZddlZddlZddlZddlZddlZddlm Z ddl
m Z ddl m
Z
ddlmZ ddlmZ ddlmZ dd lmZmZmZmZmZmZmZm Z m Z m Z dd
l m Z m!Z!m"Z"m#Z# dd l$m%Z& dd l'm(Z( dd
l)m*Z* erddl+m,Z, ej- dk rddlm.Z. nerddl/m.Z. nddl0m1Z. e e2ef Z3 e de3 Z4 ej5 e6 Z7 G d de Z8dZ9dZ: G d de Z; G d de. Z< G d d Z= G d d e= Z> G d d! Z?d"ed#e@fd$ZAd%ee2 d&ee2e2f d'ed#e@fd(ZBd) ZCd*e*d#ee2 fd+ZDd*e*d#ee2 fd,ZEd%ee2 d&ee2e2f d-e3d#ee2e2f fd.ZFd/e3d#e2fd0ZGd1ee2e2f d#ee2 fd2ZHd%ee2 d1ee2e2f d#ee e2ee2 f fd3ZId1ee2e2f d#ee2e2f fd4ZJd5e2d6e2d7e2d8e2d#e@f
d9ZKd:e3d#e2fd;ZLde2d#e2fd?ZN G d@ dAe#jO ZPdBZQd>e2dCee2e2f dDee2ee2 f d#e2fdEZR G dF dGeS ZT G dH dIe"jU ZVdS )Ja
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 SetuptoolsDeprecationWarningerrors
namespaces)build_pyfind_package_path) Distribution 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 r d}t
j |t t | 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( _modemsgs /builddir/build/BUILDROOT/alt-python311-setuptools-65.6.3-2.el9.x86_64/opt/alt/python311/lib/python3.11/site-packages/setuptools/command/editable_wheel.pyconvertz_EditableMode.convertG s} ) ( (
1 1 1$%Wt%W%W%WXX X H C
M# ; < < < U## N) __name__
__module__ __qualname____doc__STRICTr, r+ classmethodr strr6 r7 r5 r$ r$ ; s_ FG
F$8C= $_ $ $ $ [$ $ $r7 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_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=N c > d | _ d | _ d | _ d | _ d S N)dist_dir
dist_info_dir project_dirr( selfs r5 initialize_optionsz!editable_wheel.initialize_optionsv s$
! r7 c | j }|j p t j | _ |j pi | _ t
| j p$t j | j d | _ d S )Ndist)
distributionsrc_rootoscurdirrI package_dirr rG pathjoin)rK rN s r5 finalize_optionsz editable_wheel.finalize_options| sX =5BI +1r T] Tbgll4;KV.T.TUU
r7 c | j d | | d | d }| | j | | d S # t $ r<}t j
d}t j t | |d }~ww xY w)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"
)rG mkdir_ensure_dist_inforeinitialize_commandget_finalized_commandwrite_wheelfilerH _create_wheel_file Exception traceback print_excr
InternalErrorr )rK rY exr4 s r5 runzeditable_wheel.run s > M . . . " " $ $ $
% %m 4 4 4 44]CCK ' '(: ; ; ; # #K 0 0 0 0 0
>
>
> ! ! !
C &x}}552 =
>s BB
C7C
Cc f | j W| d }| j |_ | | |j | _ d S t
| j d sJ t | j d sJ d S )N dist_infoz
.dist-infoMETADATA)
rH r\ rG
output_dirensure_finalizedre r> endswithr exists)rK rg s r5 r[ z editable_wheel._ensure_dist_info s % 11+>>I#'=I & & ( ( ( MMOOO!*!8D t)**33LAA A A A*J77>>@@ @ @ @ @ @r7 c | j }|j sd S t | j | j dd }t |||| }| d S )NrD .) rO namespace_packagesr rI rS getresolve_NamespaceInstallerinstall_namespaces)rK installation_dir
pth_prefixrN rP installers r5 _install_namespacesz"editable_wheel._install_namespaces sw & F($*:*>*>r3*G*GHHPPRR'.>
HUU $$&&&&&r7 r) c | j rt | j j n
t }t t | d }t
|d S )Nz
*.egg-info)rH r parentmapr> globnext)rK
parent_dir
candidatess r5 _find_egg_info_dirz!editable_wheel._find_egg_info_dir sT 8<8JVT$,--44PTPVPV
jool ; ;<<
J%%%r7 nameunpacked_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)rO r> r r\ 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_moderj )rK r r r r rN wheelr r r r r r r r s r5 _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~ r7 dist_namec | |||| | | \ }}| d | d | d ||fS )Nr r r )r _run_build_subcommandsr _run_install)rK r r r r r r s r5 _run_build_commandsz"editable_wheel._run_build_commands s
i GLLL ##%%% 4466w )$$$ )$$$ &!!!g~ r7 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)r] r type build_py_cls _safely_run run_command)rK r r r s r5 r z%editable_wheel._run_build_subcommands s 33G<<**,, ' 'D,,T22Cz!!d3ii<&?&? &&&& &&&& ' 'r7 r c | | S # t $ r< t j d| d| d}t j |t d Y d S w xY w)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)r r` ra
format_excr0 r1 r )rK r r4 s r5 r zeditable_wheel._safely_run" s K##H-- - K K K +--
4<
'
C
M# ; J J J J J J J Ks AA A c
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 | | | |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 rg -z
0.editablez.whl)suffixz
.build-libz .build-tempw)wheel.wheelfiler r] r rU get_tagr rG rl unlinkr rH shutilcopytreerw r _select_strategy write_files)rK rY r rg r tag build_tag archive_name
wheel_pathr r build_tmpunpackedlibtmpunpacked_dist_infor r strategy wheel_objs r5 r_ z!editable_wheel._create_wheel_file6 sJ ------..{;; N hh{**,,-- #;;i;;#;;; $- 66
+<@@@&l;;; &m<<<
0x 0c9 0!%hT5G0H0H0M!N!N OD .0B C C C $ $Xy~ > > > ! 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 G5 G BG
F0 *#F
F0 F F0 F !F0 $ G0F4
4G7F4
8G; G G G G G G5 G" "G5%G" &G55G9<G9categoryc t | j d| d }|rB | r:t d| d | d| d S d S d S )Nhas_z Installing z as non editableinstall_)getattrrO _loggerinfor )rK r has_categorys r5 r zeditable_wheel._run_installR s t 02C2C2CTJJ 4LLNN 4 LLAxAAA B B B 2 2 2 3 3 3 3 3 4 4 4 4r7 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 rD rn )r rI r$ r6 r( r<
_empty_dir _LinkTreerO _find_packages_simple_layoutrS r+ setrp
_StaticPth_TopLevelFinder) rK r r r
build_namerI r(
auxiliary_dirpackageshas_simple_layoutis_compat_modesrc_dirs r5 r z editable_wheel._select_strategyX s# 2T11C11
4+,, $$TY// =' ' ' &tD, (. (&**2s33G d /['8R8R7STT T t 0$777r7 ) r8 r9 r: r; descriptionr r$ user_optionsrL rV re r[ rw r r> r _Pathr r r r
r
r r r r r_ r r r? r7 r5 rA rA i s 6K LK $ !6!<"==>L V V V > > >4 A A A' ' '&HSM & & & &
0#0#).0#;@0#KP0# 0# 0# 0#d # # # d3ic3h .G(H .3 @E PU tCy$sCx.( ) ' ' ',KC K K K K( 84S 4 4 4 4 88 8 8
8 8 8 8 8 8r7 rA c J e Zd Zdddee deeef fdZd Zd ZdS ) r r r r r c d S rF r? )rK r r r s r5 __call__zEditableStrategy.__call__t r7 c d S rF r? rJ s r5 __enter__zEditableStrategy.__enter__w r r7 c d S rF r? rK _exc_type
_exc_value
_tracebacks r5 __exit__zEditableStrategy.__exit__z r r7 N) r8 r9 r: r
r> r
r r r r? r7 r5 r r s sh k $s) d3PS8n r7 r c j e Zd Zdededee fdZdddee deeef fd Z d
Z
d Z d S )
r rN r path_entriesc 0 || _ || _ || _ d S rF )rN r r )rK rN r r s r5 __init__z_StaticPth.__init__ s (r7 r r r r c d d | j D }t | dd }| d| j d| d S )N
c 3 X K | ]%}t | V &d S rF )r> rq ).0ps r5 z&_StaticPth.__call__.. s2 I I!S - - I I I I I Ir7 utf-8r .pth)rU r byteswritestrr )rK r r r entriescontentss r5 r z_StaticPth.__call__ sb )) I It7H I I IJJG 11
6ty666AAAAAr7 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
)listrz rQ fspathr r warning_LENIENT_WARNINGrK r4 s r5 r z_StaticPth.__enter__ sQ
c")T .// 0 0 ../// r7 c d S rF r? r s r5 r z_StaticPth.__exit__ r r7 N) r8 r9 r: r r> r
r r r
r r r r? r7 r5 r r ~ s )\ ) )DJ ) ) ) )
Bk B$s) Bd3PS8n B B B B
r7 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.
rN r r r c t | | _ t | | _ | d j | _ t ||| j g d S )Nr ) r r rq r r copy_file_filesuperr )rK rN r r r __class__s r5 r z_LinkTree.__init__ sn "- 0 0 i 0022))*55?
td&8%9:::::r7 r r r r c z | || t ||| d S rF )
_create_linksr r )rK r r r r s r5 r z_LinkTree.__call__ s; 5'***
w/////r7 filer) c * t t 5 t | | j }t
| t j d cd d d S # 1 swxY w Y d S )N/)
r
ValueErrorr rq relative_tor r> replacerQ sep)rK r rT s r5 _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 ry is_dirrZ r )rK r r! r% dests r5 _create_filez_LinkTree._create_file s\ !O3{!!## , K d + + +
8T
-----r7 c j dd t j rdnd} fd| D }| d d |D ]3} | }|r||vr || 4| D ] \ }} ||| d S )NT)r# rX symhardc B i | ]\ }} | | S r? )r )r kvrK s r5
z+_LinkTree._create_links.. s=
1
" "1 % %q
r7 r$ )r rZ _can_symlink_filesitemspopr r( )rK outputsoutput_mapping link_typemappingsoutputrelativesrcs ` r5 r z_LinkTree._create_links s === /0B C COEE
&,,..
T4 4 4F--f55H
4HH 4 4!!(F333 %^^ - - = =MHc h) < < < < = =r7 c N d}t |t z | S )Nz=Strict editable install will be performed using a link tree.
)r r _STRICT_WARNINGr s r5 r z_LinkTree.__enter__ s# No-... r7 c P d| j d}t j |t 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.
)r r0 r1 InformationOnlyrK r r r r4 s r5 r z_LinkTree.__exit__ s8
c?+++++r7 rF )r8 r9 r: r; r r> r r r
r
r r r r( r r r
__classcell__)r s @r5 r r s% ; ; ; ; ; ; ; ; ; ;0k 0$s) 0d3PS8n 0 0 0 0 0 0c hsm . .C .3 . . . . = = ="
, , , , , , ,r7 r c Z e Zd ZdedefdZdddee deeef fdZd Z d
Z
d S ) r rN r c " || _ || _ d S rF )rN r )rK rN r s r5 r z_TopLevelFinder.__init__ s r7 r r r r c | j j p t j }t t | j t
| j }| j j pi }t ||| }t t t | j j pg | d t | D }d| j
d} t | }
t t! | || d } | |
d| t d|
d|
dd } | d| j
d | d S )
Nc 3 K | ]}|g fV d S rF r? )r nss r5 r z+_TopLevelFinder.__call__.. s& @ @"b"X @ @ @ @ @ @r7 r z.finderr z.pyzimport z; z
.install()r )rN rP rQ rR r r _find_top_level_modulesrS _find_package_rootsdict_find_namespacesr _find_virtual_namespacesr _make_identifierr _finder_templater ) rK r r r rP top_levelrS roots namespaces_r findercontents r5 r z_TopLevelFinder.__call__ sE 9%2.335LTY5W5WXX i+1r #I{HEE,0 TY / 52u = = @ @ 8 ? ? @ @ @2
2
- -
2ty111!$''(ukBBGLL
&~~~w///>&>>F>>>HH
6ty666@@@@@r7 c N d}t |t z | S )Nz=Editable install will be performed using a meta path finder.
)r r r
r s r5 r z_TopLevelFinder.__enter__ s$ N ../// r7 c > d}t j |t d S )Nz
Please be careful with folders in your working directory with the same
name as your package as they may take precedence during imports.
)r0 r1 r= r> s r5 r z_TopLevelFinder.__exit__ s#
c?+++++r7 N) r8 r9 r: r r> r r
r
r r r r? r7 r5 r r s \ Ak A$s) Ad3PS8n A A A A&
, , , , ,r7 r base_dirr) c t t | 5 }t |d t |d }}| dd t t t t 5 t j
|| | r3| d dk r d d d d d d dS d d d n # 1 swxY w Y t j
|| n$# t $ r}d}t | |d }~ww xY w d d d d S # 1 swxY w Y d S )
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)r r> rq r
write_textr AttributeErrorNotImplementedErrorOSErrorrQ symlink
is_symlink read_textr% r` LinksNotSupported)rS r path1path2rd r4 s r5 r0 r0 s H$4$4$6$6 7 7 8 8 8 CC--tC/E/Eu
7333
n&97
C
C Jue $ $ $ !!
eoowo&G&G7&R&R
1 GE5 ! ! ! ! 1 1 1P
$C((b 0 1 ! sa AEAC1
E% E1C5 5E8C5 9E=DE
D4 D//D44EE E r rS rI c " fd| D }|st i dhfv S t j d | D t fd| D S )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
c 4 i | ]}|t | S r? r )r pkgrS rI s r5 r/ z"_simple_layout..4 s8
sK
=
= r7 rD c 4 g | ]\ }}t || S r? ) _parent_path)r r- r. s r5
z"_simple_layout..: s& O O O1 a!3!3 O O Or7 c 3 K | ]E\ }}t t g| d R t | k V FdS rn N)_normalize_pathr split)r keyvaluery s r5 r z!_simple_layout..; sj C V5ciinn55566/%:P:PP r7 )r rQ rT
commonpathr1 all)r rS rI layoutry s `` @r5 r r s > F .; B:--
W
O O O O O
P
PF ,,.. r7 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 )rk lenrstriprQ r )rd pkg_pathry s r5 rf rf A sJ &.%6%6s%;%;
IXjCyj
!
!F ==rv & &&r7 rN 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 rn r? r mods r5 rg z"_find_packages..S s >>>c3#::c:::r7 c . g | ]}d |j v |j S rw r r xs r5 rg z"_find_packages..X s! HHHa#--16---r7 rn )iterr
py_modules ext_package ext_modules
rpartition)rN r nested_modulesr modulepackage_s r5 r r O s DM'R((((((((( &BJ>>Z>>>N I &," HH;HHHH ))#..
A
r7 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 ri r? rx s r5 r z*_find_top_level_modules..a s& <<S^^^^^^<.e s0 EEq3af3D3DAF3D3D3D3DEEr7 )r r r )rN r r s r5 rE rE _ s &BJ<.m s@ ! ! ! ^ -c; I I
J
J! ! !r7 )sorted_remove_nested)r rS rP pkg_rootss `` r5 rF rF h sI
! ! ! ! !(##! ! !I
) $ $$r7 rT c t | }|j }| r!t | S t | |j z S )z(Works for packages and top-level modules)r ry rl r> rq r )rT path_ry s r5 r r u sY JJE
\F ||~~ 25==??###6>>##ej0111r7 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.
rn r NrD )rk rangerr rU r r rl )r rd partsi partial_namerT s r5 rI rI s # # c>> #s5zzA~q"-- # #A 88E"1"I..L), 2FFGGD;;==
#L $A$A"""" # # #r7 c # K | D ]]}t ||d }t | r)t |d s||gfV ^d S )NrD z __init__.py)r r rl )r r rd rT s r5 rH rH s| i44 :: tD-'@'@'G'G'I'I - r7 c : t | }t t | D ]H\ t fd| D r| I|S )Nc 3 N K | ] \ }}|k ot || V d S rF )
_is_nested)r other
other_pathrT rd s r5 r z!_remove_nested.. sR
!z
5L EZT5* E E
r7 )rG copyreversedr
r1 anyr2 )r r7 rT rd s @@r5 r r s
)..""
#
#F d9??#4#4 5 566 T
%.__%6%6
JJsOOO Mr7 rd rt ry parent_pathc t | }| |dd d d }| | o |t 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
rD r rn )rj r striprk
startswithr )rd rt ry r
norm_pkg_pathrests r5 r r s| $H--M ;;vr1 % % + +C 0 0 6 6s ; ;D v G _T+-E-E-E-E F F Fr7 filenamec t j dk r t j | n| }t j t j t j | S )z1Normalize a file/dir name for comparison purposescygwin)sysplatformrQ rT abspathnormcaserealpathnormpath)r r s r5 rj rj s^ ), (@(@27??8 $ $ $hD
7 BG , ,RW-=-=d-C-C D D E EEr7 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 rmtreerQ makedirs)r s r5 r r s,
M$d++++K Kr7 r c ^ t j dd| }| sJ |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)r )resub isidentifier)r safes r5 rJ rJ s4 6-d + +D Kr7 c e Zd Zd Zd Zd ZdS )rr c Z || _ || _ || _ || _ g | _ d| _ d S )NF)rO rP rt
editable_namer3 dry_run)rK rO rt r rP s r5 r z _NamespaceInstaller.__init__ s3 (
0 * r7 c V t j | j | j S )zInstallation target.)rQ rT rU rt r rJ s r5 _get_targetz _NamespaceInstaller._get_target s w||D 143EFFFr7 c D t t | j S )z1Where the modules/packages should be loaded from.)reprr> rP rJ s r5 _get_rootz _NamespaceInstaller._get_root s C
&&'''r7 N)r8 r9 r: r r r r? r7 r5 rr rr sD G G G( ( ( ( (r7 rr a< 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 r c t t | d }t | || S )z_Create a string containing the code for the``MetaPathFinder`` and
``PathEntryFinder``.
c | d S )Nr r? )r s r5 z"_finder_template..? s
1 r7 )rl r r r )rG r r1 _FINDER_TEMPLATEformatr s r5 rK rK 9 sC 6'--//~~>>>??G " "g* " U UUr7 c e Zd ZdZdS )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...
Nr8 r9 r: r; r? r7 r5 r= r= C s r7 r= c e Zd ZdZdS )r_ zCFile system does not seem to support either symlinks or hard links.Nr r? r7 r5 r_ r_ K s MMMMr7 r_ )Wr; loggingrQ r r r ra r0
contextlibr enumr inspectr itertoolsr pathlibr tempfiler typingr r
r r r
r r r r r
setuptoolsr r r r setuptools.command.build_pyr r setuptools.discoveryr setuptools.distr r r version_infor typing_extensionsabcr r> r r! getLoggerr8 r r$ r; r
rA r r r r boolr0 r rf r rE rF r rI rH r r rj r rJ Installerrr r rK UserWarningr= FileErrorr_ r? r7 r5 r s
' ' ' ' ' ' Q P P P P P P P P P P P @ @ @ @ @ @ 2 2 2 2 2 2 ( ( ( ( ( ( *))))))v $*******######
c4i WT
'
H
%
%!$ !$ !$ !$ !$D !$ !$ !$H G8 G8 G8 G8 G8W G8 G8 G8T x .D, D, D, D, D,
D, D, D,N", ", ", ", ", ", ", ",J $ ()sm)*.sCx.)GK) ) ) ) )X ' ' '
(3-
F, F8C= F F F F
%sm
%c"
%
%
#s(^
%
%
%
%2 23 2 2 2 2#S#X #8C= # # # #0 3i $(cN
eCcN#$
d38n
c3h
C 3 # $ .Fe F F F F FR B 3 3 ( ( ( ( (*. ( ( ($E PV
V S)V7;CcN7KVV V V V k N N N N N( N N N N Nr7