_i# B d Z ddlZddlZddlZddlZddlZddlm Z ddl
m Z ddl
mZmZ ddl
mZ ddlmZ dd lmZmZ dd
lmZ dd lmZ dd lm Z g d
Z ej< Z dZ ej@ Z!ej@ Z"d Z#d Z$d Z%ejL jJ j e%_ ejN ejL jP Z) G d de) Z(d Z*ejV fdZ, ejZ e d Z G d de. Z/ ej` y)z@Extensions to the 'distutils' for large or complex distributions N)DistutilsOptionError) convert_path )loggingmonkey)version)Require)
PackageFinderPEP420PackageFinder) Distribution) Extension) SetuptoolsDeprecationWarning)setupr Commandr
r r
find_packagesfind_namespace_packagesc G d dt j j } || }|j d |j r t | y y )Nc 4 e Zd ZdZ fdZd fd Zd Z xZS )4_install_setup_requires..MinimalDistributionzl
A minimal version of a distribution for supporting the
fetch_build_eggs interface.
c d}t | t | z D ci c] }|||
}}t | | | j j y c c}w )N)dependency_linkssetup_requires)setsuper__init__ set_defaults_disable)selfattrs_inclkfiltered __class__s /builddir/build/BUILDROOT/alt-python312-setuptools-69.0.2-3.el8.x86_64/opt/alt/python312/lib/python3.12/site-packages/setuptools/__init__.pyr z=_install_setup_requires..MinimalDistribution.__init__1 sX 8E-0Z#e*-DE-D58 -DHE G X & & & ( Fs
Ac X t | | \ }}|dfS # t $ r |dfcY S w xY w)zAIgnore ``pyproject.toml``, they are not related to setup_requires )r _split_standard_project_metadata Exception)r filenamescfgtomlr# s r$ _get_project_config_fileszN_install_setup_requires..MinimalDistribution._get_project_config_files8 s=
% !G DY O TBw
% "}$
%s
))c y)zl
Disable finalize_options to avoid building the working set.
Ref #2158.
Nr& )r s r$ finalize_optionszE_install_setup_requires..MinimalDistribution.finalize_options@ s N)__name__
__module__ __qualname____doc__r r, r.
__classcell__r# s @r$ MinimalDistributionr + s
) % r/ r7 T)ignore_option_errors) distutilscorer parse_config_filesr _fetch_build_eggs)r r7 dists r$ _install_setup_requiresr> ( sM inn 9 9 6 u %D 6 $ r/ c | j | j y # t $ rS}d}d|j j v r3t |d r|j
| | j d| d d }~ww xY w)Na
It is possible a package already installed in your system
contains an version that is invalid according to PEP 440.
You can try `pip install --use-pep517` as a workaround for this problem,
or rely on a new virtual environment.
If the problem refers to a package that is not installed yet,
please contact that package's maintainers or distributors.
InvalidVersionadd_note
)fetch_build_eggsr r( r# r1 hasattrrA announce)r= exmsgs r$ r< r< N sz d 1 12 r|| 4 4 4r:& C
3%rl+
s A:AA55A:c ~ t j t | t j j
di | S )Nr& )r configurer> r9 r: r )r s r$ r r c s. E" >> (% ((r/ c < e Zd ZdZdZ fdZddZd ZddZ xZ S ) r a
Setuptools internal actions are organized using a *command design pattern*.
This means that each action (or group of closely related actions) executed during
the build should be implemented as a ``Command`` subclass.
These commands are abstractions and do not necessarily correspond to a command that
can (or should) be executed via a terminal, in a CLI fashion (although historically
they would).
When creating a new command from scratch, custom defined classes **SHOULD** inherit
from ``setuptools.Command`` and implement a few mandatory methods.
Between these mandatory methods, are listed:
.. method:: initialize_options(self)
Set or (reset) all options/attributes/caches used by the command
to their default values. Note that these values may be overwritten during
the build.
.. method:: finalize_options(self)
Set final values for all options/attributes used by the command.
Most of the time, each option/attribute/cache should only be set if it does not
have any value yet (e.g. ``if self.attr is None: self.attr = val``).
.. method:: run(self)
Execute the actions intended by the command.
(Side effects **SHOULD** only take place when ``run`` is executed,
for example, creating new files or writing to the terminal output).
A useful analogy for command classes is to think of them as subroutines with local
variables called "options". The options are "declared" in ``initialize_options()``
and "defined" (given their final values, aka "finalized") in ``finalize_options()``,
both of which must be defined by every command class. The "body" of the subroutine,
(where it does all the work) is the ``run()`` method.
Between ``initialize_options()`` and ``finalize_options()``, ``setuptools`` may set
the values for options/attributes based on user's input (or circumstance),
which means that the implementation should be careful to not overwrite values in
``finalize_options`` unless necessary.
Please note that other commands (or other parts of setuptools) may also overwrite
the values of the command's options/attributes multiple times during the build
process.
Therefore it is important to consistently implement ``initialize_options()`` and
``finalize_options()``. For example, all derived attributes (or attributes that
depend on the value of other attributes) **SHOULD** be recomputed in
``finalize_options``.
When overwriting existing commands, custom defined classes **MUST** abide by the
same APIs implemented by the original class. They also **SHOULD** inherit from the
original class.
Fc X t | | t | j | y)zj
Construct the command for dist, updating
vars(self) with any keyword parameters.
N)r r varsupdate)r r= kwr# s r$ r zCommand.__init__ s$
T
" r/ c t | | }|t | || |S t |t st d|d|d|d |S )N'z ' must be a z (got `z`))getattrsetattr
isinstancestrr )r optionwhatdefaultvals r$ _ensure_stringlikezCommand._ensure_stringlike sL dF# ; D&' *NC%&28$D
r/ c t | | }|yt |t r"t | |t j
d| yt |t rt d |D }nd}|st d|d|d y)a Ensure that 'option' is a list of strings. If 'option' is
currently a string, we split it either on /,\s*/ or /\s+/, so
"foo bar baz", "foo,bar,baz", and "foo, bar baz" all become
["foo", "bar", "baz"].
..
TODO: This method seems to be similar to the one in ``distutils.cmd``
Probably it is just here for backward compatibility with old Python versions?
:meta private:
Nz,\s*|\s+c 3 < K | ] }t |t y wr0 )rS rT ).0vs r$ z-Command.ensure_string_list.. s 9SAs+Ss FrP z!' must be a list of strings (got )) rQ rS rT rR resplitlistallr )r rU rX oks r$ ensure_string_listzCommand.ensure_string_list su dF# ;
S
! D&"((;"< =#t$9S99*AGM r/ c h t j | || }t | j | |S r0 )_Commandreinitialize_commandrL rM )r commandreinit_subcommandsrN cmds r$ rh z Command.reinitialize_command s. ++D';MN S
r/ r0 )r )
r1 r2 r3 r4 command_consumes_argumentsr rY re rh r5 r6 s @r$ r r p s% 4l "' 6r/ r c d t j | d D }t t j j | S )z%
Find all files under 'path'
c 3 r K | ]/ \ }}}|D ]$ }t j j || & 1 y wr0 )ospathjoin)r\ basedirsfilesfiles r$ r^ z#_find_all_simple.. s; !@ D$D T4 !!@s 57T) followlinks)ro walkfilterrp isfile)rp resultss r$ _find_all_simpler{ s3 !#4!@G
"''..' **r/ c t | }| t j k( r;t j t j
j | }t || }t | S )z
Find all files under 'dir' and return the list of full filenames.
Unless dir is '.', return full filenames with dir prepended.
)start) r{ ro curdir functoolspartialrp relpathmaprb )dirrt make_rels r$ findallr sJ
S !E
bii $$RWW__C@He$ ;r/ c H t j ddd t | S )Nz Access to implementation detaila
The function `convert_path` is not provided by setuptools itself,
and therefore not part of the public API.
Its direct usage by 3rd-party packages is considered improper and the function
may be removed in the future.
)i
)due_date)r emit
_convert_path)pathnames r$ r r s* %%)
""r/ c e Zd ZdZy)sicz;Treat this string as-is (https://en.wikipedia.org/wiki/Sic)N)r1 r2 r3 r4 r& r/ r$ r r s Er/ r )1r4 r ro r` _distutils_hack.override_distutils_hackdistutils.corer9 distutils.errorsr distutils.utilr r r r r _version_moduledependsr discoveryr
r r= r extensionr
warningsr __all__ __version__bootstrap_install_fromfindr r r> r< r r:
get_unpatchedr rg r{ r~ r wrapsrT r patch_allr& r/ r$ r s F 1 8 ( 9 2 )) ""
-22 # L*) $$,,
6 6 6 7jh jZ + # # F# F
r/