1j
O U d Z ddlmZ ddlZddlZddlZddlZddlZddlZddl Z ddl
Z
ddl Z ddl m
Z
mZmZ ddlmZ ddlmZmZmZ ddlZddlmZ dd lmZmZ dd
l m Z dd l m Z ddl Z dd l m!Z! erdd
l"m#Z# g dZ$ G d de% Z& G d dej' j( Z(ej) d Z*d Z+d&dZ,d Z-ej) d Z.eee/ee/e0e/ df f df Z1d e2d < G d d Z3 G d d!e3 Z4 G d" d#e4 Z5 G d$ d%e Z6 e4 Z7e7j8 Z8e7j9 Z9e7j: Z:e7j; Z;e7j< Z Z>e7j? Z? e5 Z@dS )'a' A PEP 517 interface to setuptools
Previously, when a user or a command line tool (let's call it a "frontend")
needed to make a request of setuptools to take a certain action, for
example, generating a list of installation requirements, the frontend
would call "setup.py egg_info" or "setup.py bdist_wheel" on the command line.
PEP 517 defines a different method of interfacing with setuptools. Rather
than calling "setup.py" directly, the frontend should:
1. Set the current directory to the directory with a setup.py file
2. Import this module into a safe python interpreter (one in which
setuptools can potentially set global variables or crash hard).
3. Call one of the functions defined in PEP 517.
What each function does is defined in PEP 517. However, here is a "casual"
definition of the functions (this definition should not be relied on for
bug reports or API stability):
- `build_wheel`: build a wheel in the folder and return the basename
- `get_requires_for_build_wheel`: get the `setup_requires` to build
- `prepare_metadata_for_build_wheel`: get the `install_requires`
- `build_sdist`: build an sdist in the folder and return the basename
- `get_requires_for_build_sdist`: get the `setup_requires` to build
Again, this is not a formal definition! Just a "taste" of the module.
) annotationsN)IterableIteratorMapping)Path)
TYPE_CHECKINGNoReturnUnion )errors)StrPath same_path)
parse_strings) SetuptoolsDeprecationWarning) strtobool) TypeAlias)
get_requires_for_build_sdist get_requires_for_build_wheel prepare_metadata_for_build_wheel build_wheel build_sdist get_requires_for_build_editable#prepare_metadata_for_build_editablebuild_editable
__legacy__SetupRequirementsErrorc e Zd ZddZdS )r returnNonec || _ d S N)
specifiers)selfr" s g/builddir/build/BUILD/cloudlinux-venv-1.0.11/venv/lib/python3.11/site-packages/setuptools/build_meta.py__init__z SetupRequirementsError.__init__H s
$ N)r r )__name__
__module__ __qualname__r% r& r$ r r G s( % % % % % %r& r c H e Zd ZddZeej dd ZdS ) Distributionr r c X t t | }t | r! )listr r )r# r" specifier_lists r$ fetch_build_eggsz Distribution.fetch_build_eggsM s% mJ 7 788$^444r& Iterator[None]c # K t j j }| t j _ dV |t j _ dS # |t j _ w xY w)zw
Replace
distutils.dist.Distribution with this class
for the duration of this context.
N) distutilscorer, )clsorigs r$ patchzDistribution.patchR sP ~*&) # / EEE*.IN ' ' '$IN ' . . . .s = AN)r r )r r1 )r' r( r) r0 classmethod
contextlibcontextmanagerr7 r* r& r$ r, r, L sV 5 5 5 5
/ / / [ / / /r& r, c # K t j } d t _ dV | t _ dS # | t _ w xY w)a
Temporarily disable installing setup_requires
Under PEP 517, the backend reports build dependencies to the frontend,
and the frontend is responsible for ensuring they're installed.
So setuptools (acting as a backend) should not try to install them.
c d S r! r* )attrss r$ z+no_install_setup_requires..k s t r& N)
setuptools_install_setup_requires)r6 s r$ no_install_setup_requiresrA b sK -D););J&2
-1
***T
*1111s / =c D fdt j D S )Nc g | ]A}t j t j | ?|BS r* )ospathisdirjoin).0namea_dirs r$
z1_get_immediate_subdirectories..s sM bgmmBGLLPTz'_file_with_extension..y s4 JJaAJJy4I4IJJJJJJJr& z[No distribution was found. Ensure that `setup.py` is not empty and that it calls `setup()`.)rD rL
ValueError)rN rO matchingfiles ` r$ _file_with_extensionrZ x sr JJJJ2:i00JJJH
8
Ks ( Ac t j | st j d S t j | S )Nz%from setuptools import setup; setup())rD rE existsioStringIOtokenizeopen setup_scripts r$ _open_setup_scriptrc s:
7>>, ' ' D{BCCC = & &&r& c # K t j 5 t j dd d V d d d d S # 1 swxY w Y d S )Nignorez setup.py install is deprecated)warningscatch_warningsfilterwarningsr* r& r$ suppress_known_deprecationri s " " *JKKK
s =AAr _ConfigSettingsc : e Zd ZdZddZdd
Zdd Zdd Zdd
ZdS )_ConfigSettingsTranslatorzTranslate ``config_settings`` into distutils-style command arguments.
Only a limited number of options is currently supported.
keystrconfig_settingsrj r list[str]c |pi }| | pg }t |t rt j | n|S )aA
Get the value of a specific key in ``config_settings`` as a list of strings.
>>> fn = _ConfigSettingsTranslator()._get_config
>>> fn("--global-option", None)
[]
>>> fn("--global-option", {})
[]
>>> fn("--global-option", {'--global-option': 'foo'})
['foo']
>>> fn("--global-option", {'--global-option': ['foo']})
['foo']
>>> fn("--global-option", {'--global-option': 'foo'})
['foo']
>>> fn("--global-option", {'--global-option': 'foo bar'})
['foo', 'bar']
)get
isinstancern shlexsplit)r# rm ro cfgoptss r$ _get_configz%_ConfigSettingsTranslator._get_config sF $ #wws||!r$.tS$9$9Cu{4 tCr&
Iterator[str]c # K |pi }h d}d|v sd|v rUt | d p| d pd }| |v rdndV d|v sd|v rUt | d p| d pd }| |v rdndV | d | E d
{V d
S ) a
Let the user specify ``verbose`` or ``quiet`` + escape hatch via
``--global-option``.
Note: ``-v``, ``-vv``, ``-vvv`` have similar effects in setuptools,
so we just have to cover the basic scenario ``-v``.
>>> fn = _ConfigSettingsTranslator()._global_args
>>> list(fn(None))
[]
>>> list(fn({"verbose": "False"}))
['-q']
>>> list(fn({"verbose": "1"}))
['-v']
>>> list(fn({"--verbose": None}))
['-v']
>>> list(fn({"verbose": "true", "--global-option": "-q --no-user-cfg"}))
['-v', '-q', '--no-user-cfg']
>>> list(fn({"--quiet": None}))
['-q']
> 0noofffalseverbosez --verbose1z-qz-vquietz--quietz--global-optionN)rn rr lowerrx )r# ro rv falseylevels r$ _global_argsz&_ConfigSettingsTranslator._global_args s * #,,, {c 1 1 **Icggk.B.BIcJJE ;;==F2244 = = = c>>Y# - -((ECGGI,>,>E#FFE ;;==F2244 = = =##$5GGGGGGGGGGGr& c # K |pi }d|v r,t t |d pd }|rdndV d|v r dt |d gE d{V dS dS )a
The ``dist_info`` command accepts ``tag-date`` and ``tag-build``.
.. warning::
We cannot use this yet as it requires the ``sdist`` and ``bdist_wheel``
commands run in ``build_sdist`` and ``build_wheel`` to reuse the egg-info
directory created in ``prepare_metadata_for_build_wheel``.
>>> fn = _ConfigSettingsTranslator()._ConfigSettingsTranslator__dist_info_args
>>> list(fn(None))
[]
>>> list(fn({"tag-date": "False"}))
['--no-date']
>>> list(fn({"tag-date": None}))
['--no-date']
>>> list(fn({"tag-date": "true", "tag-build": ".a"}))
['--tag-date', '--tag-build', '.a']
ztag-dater~ z
--tag-datez --no-datez tag-buildz --tag-buildN)r rn )r# ro rv vals r$ __dist_info_argsz*_ConfigSettingsTranslator.__dist_info_args s & # CJ :7 ; ;<>> fn = _ConfigSettingsTranslator()._editable_args
>>> list(fn(None))
[]
>>> list(fn({"editable-mode": "strict"}))
['--mode', 'strict']
z
editable-mode
editable_modeNz--mode)rr rn )r# ro rv modes r$ _editable_argsz(_ConfigSettingsTranslator._editable_args sj #ww''C377?+C+C F c$ii((((((((((r& c # B K | d| E d{V dS )av
Users may expect to pass arbitrary lists of arguments to a command
via "--global-option" (example provided in PEP 517 of a "escape hatch").
>>> fn = _ConfigSettingsTranslator()._arbitrary_args
>>> list(fn(None))
[]
>>> list(fn({}))
[]
>>> list(fn({'--build-option': 'foo'}))
['foo']
>>> list(fn({'--build-option': ['foo']}))
['foo']
>>> list(fn({'--build-option': 'foo'}))
['foo']
>>> list(fn({'--build-option': 'foo bar'}))
['foo', 'bar']
>>> list(fn({'--global-option': 'foo'}))
[]
z--build-optionN)rx r# ro s r$ _arbitrary_argsz)_ConfigSettingsTranslator._arbitrary_args
s7 * ##$4oFFFFFFFFFFFr& N)rm rn ro rj r rp )ro rj r ry ) r' r( r) __doc__rx r )_ConfigSettingsTranslator__dist_info_argsr r r* r& r$ rl rl s D D D D, H H H H@> > > >4) ) ) ) G G G G G Gr& rl c e Zd Zd(dZd)d*d Z d+d,d
Z d+d,dZd-dZd.dZ d+d/dZ d0d1d Z
d2d3d Z d+d4d"Z d5d$Z
d2d3d%Z d+d,d&Z d+d/d'Zd S )6_BuildMetaBackendro rj requirementsrp c D g t j d d | | dt _ t 5 | d d d n # 1 swxY w Y n!# t $ r}||j z
}Y d }~nd }~ww xY w|S )Nr egg_info)sysargvr r, r7 run_setupr r" )r# ro r es r$ _get_build_requiresz%_BuildMetaBackend._get_build_requires# s
Xbqb\
/
/
) ##%%
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!% ) ) ) AL (LLLLLL ) s; A? A3' A? 3A77A? :A7;A? ?
B
BB setup.pyrb rn r r c t j | }d}t | 5 }| dd }d d d n # 1 swxY w Y t
|t d S # t $ r*}|j r t j ddd Y d }~d S d }~ww xY w)N__main__z\r\nz\nz6Running `setup.py` directly as CLI tool is deprecated.znPlease avoid using `sys.exit(0)` or similar statements that don't fit in the paradigm of a configuration file.zAhttps://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html)see_url) rD rE abspathrc readreplaceexeclocals
SystemExitcoder emit)r# rb __file__r' rU r r s r$ r z_BuildMetaBackend.run_setup3 s* 7??<00
)
) 4Q6688##GU33D 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 vxx
v
( -HJ+
s) )A&&A*-A*2 B
C B??CNc 0 | |g S N)r r r s r$ r z._BuildMetaBackend.get_requires_for_build_wheelJ ''b'IIIr& c 0 | |g S r r r s r$ r z._BuildMetaBackend.get_requires_for_build_sdistO r r& metadata_directoryr
suffixc | || }t |j | s"t j t | | |j S )z
PEP 517 requires that the .dist-info directory be placed in the
metadata_directory. To comply, we MUST copy the directory to the root.
Returns the basename of the info directory, e.g. `proj-0.0.0.dist-info`.
)_find_info_directoryr parentshutilmovern rI )r# r r info_dirs r$ _bubble_up_info_directoryz+_BuildMetaBackend._bubble_up_info_directoryT sP ,,-?HH *<== ; KH
'9 : : :} r& r c p t j | D ]\ }}}fd|D }t | dk st | dk rKt | dk s J d dt | d| t ||d c S d d| }t j | ) Nc > g | ]}| |S r* rS )rH rU r s r$ rK z:_BuildMetaBackend._find_info_directory..e s* @@@QZZ-?-?@!@@@r& r r z Exactly one z& should have been produced, but found z: zNo z directory found in )rD walklenr r
InternalError)r# r r r dirs_
candidatesmsgs ` r$ r z&_BuildMetaBackend._find_info_directoryc s !w'9 : : 3 3OFD!@@@@T@@@J:!##s4yyA~~:!+++p6ppQTU_Q`Q`ppdnpp ,++ FJqM22222 (6 EFDD0BDD"3'''r& c b g t j d d | | ddt | dt _ t 5 | d d d n # 1 swxY w Y | |d | |d S )Nr dist_infoz --output-dirz--keep-egg-infoz .egg-infoz
.dist-info)r r r rn rA r r r# r ro s r$ r z2_BuildMetaBackend.prepare_metadata_for_build_wheelp s
Xbqb\
/
/
" # #
'
(
( NN
&&'9;GGG--.@,OOOs A::A>A>r*
setup_command
Iterable[str]result_extensionrP result_directoryarbitrary_argsc t j | }t j |d t j d| 5 }g t j d d | | |d||t _ t 5 |
d d d n # 1 swxY w Y t || }t j || }t j
| rt j | t j t j || | d d d n # 1 swxY w Y |S )NT)exist_okz.tmp-)prefixdirr z
--dist-dir)rD rE r makedirstempfileTemporaryDirectoryr r r rA r rZ rG r\ removerename) r# r r r ro r tmp_dist_dirresult_basename result_paths r$ _build_with_temp_dirz&_BuildMetaBackend._build_with_temp_dir s 7??+;<< $t4444
( 0
P
"1" ""?33
CH +,,
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
! 3._build s +--
00##(( 99
s ,A A
A
bdist_wheel--dist-info-dirz --dist-info-dir not recognized)r rp )rn r _IncompatibleBdistWheelr )r# r ro r r exs ``` r$ r z _BuildMetaBackend.build_wheel s %6=/** * +6=*;SAS=T=TUVV V + + +/s2ww>> # ( ( * * *6=/** * * * * * * +s 6
B 6A<6B<Bsdist_directoryc 6 | g dd|| S )N)sdistz --formatsgztarz.tar.gz)r )r# r ro s r$ r z _BuildMetaBackend.build_sdist s+ (( + + +Y
r&
str | Nonec |sd S t t | d }t | dk sJ |rt |d nd S )Nz *.dist-infor r )r. r globr rn )r# r dist_info_candidatess r$ _get_dist_info_dirz$_BuildMetaBackend._get_dist_info_dir sl ! 4 #D);$<$<$A$A-$P$P Q Q '((A----/CMs'*+++Mr& c | | }|rd|gng }dg|| | }t 5 | |d|| cd d d S # 1 swxY w Y d S )Nr editable_wheelr )r r ri r )r# r ro r r rw r s r$ r z _BuildMetaBackend.build_editable s **+=>>08@!8,,b N$N)<)<_)M)MN
'
)
) ,,V_o s A++A/2A/c , | | S r! )r r s r$ r z1_BuildMetaBackend.get_requires_for_build_editable s 00 AAAr& c . | || S r! )r r s r$ r z5_BuildMetaBackend.prepare_metadata_for_build_editable s! 44
r& )ro rj r rp r rb rn r r r! )ro rj r rp )r r
r rn r rn )r r
r rn r r )r r
ro rj r rn )r* )
r r r rP r r
ro rj r r )NN)r r
ro rj r r r rn )r r
ro rj r rn )r r r r )r' r( r) r r r r r r r r r r r r r r r* r& r$ r r " s 0 26J J J J J 26J J J J J
( ( ( ( OSP P P P P. )+
" " " " " N ,0-1 + + + + +: LP
N N N N ,0-1
26B B B B B OS
r& r c & e Zd ZdZdd fd
Z xZS )
_BuildMetaLegacyBackendaO Compatibility backend for setuptools
This is a version of setuptools.build_meta that endeavors
to maintain backwards
compatibility with pre-PEP 517 modes of invocation. It
exists as a temporary
bridge between the old packaging mechanism and the new
packaging mechanism,
and will eventually be removed.
r rb rn r r c t t j }t j t j | }|t j vr t j d| t j d }|t j d< t | |t j d d < |t j d< d S # |t j d d < |t j d< w xY w)Nr ra )
r. r rE rD dirnamer insertr superr )r# rb sys_path
script_dir
sys_argv_0 __class__s r$ r z!_BuildMetaLegacyBackend.run_setup s >>W__RW__\%B%BCC
SX % % HOOAz * * *
Xa[
" % GG < 8 8 8 #CHQQQK$CHQKKK #CHQQQK$CHQK $ $ $ $s '"C+ +"D
r r )r' r( r) r r
__classcell__)r s @r$ r r sL % % % % % % % % % % %r& r c e Zd ZdZdZdZdZdS )r zAwheel.bdist_wheel is deprecated, please import it from setuptoolsz|
Ensure that any custom bdist_wheel implementation is a subclass of
setuptools.command.bdist_wheel.bdist_wheel.
)i
z&https://github.com/pypa/wheel/pull/631N)r' r( r) _SUMMARY_DETAILS _DUE_DATE_SEE_URLr* r& r$ r r s& RHH I7HHHr& r )rN r
rO rP )Ar
__future__r r9 r] rD rt r r r r_ rf collections.abcr r r pathlibr typingr r r
r? r _pathr
r _reqsr r r3 distutils.utilr typing_extensionsr __all__
BaseExceptionr distr, r: rA rM rZ rc ri rn r. rj __annotations__rl r r r _BACKENDr r r r r r r r r r* r& r$ r s 8 # " " " " "
7 7 7 7 7 7 7 7 7 7 1 1 1 1 1 1 1 1 1 1 % % % % % % % % 2 2 2 2 2 2 $ $ $ $ $ $ ,++++++ % % % % %] % % %
/ / / / /:?/ / / /, 2 2 2 ' ' ' #73c49d6J0K+K#Ld#R S S S S S |G |G |G |G |G |G |G |G~F
F
F
F
F
1 F
F
F
R%% %% %% %% %% / %% %% %%P8 8 8 8 8 : 8 8 8 ' D ' D #+#L " " "*"J &.&R #( %
$
&
&
r&