W3BS 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%ej& j% j e%_ ej' ej& j( Z) G d de) Z(d Z*ej+ fdZ, ej- e d Z G d de. Z/ ej0 dS )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 } || }| d |j rt | d S d S )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}fdt | t z D }t | | j d S )N)dependency_linkssetup_requiresc " i | ] }|| S r ).0kattrss s/builddir/build/BUILD/imunify360-venv-2.6.2/opt/imunify360/venv/lib/python3.11/site-packages/setuptools/__init__.py
zQ_install_setup_requires..MinimalDistribution.__init__..3 s EEE58EEE )setsuper__init__ set_defaults_disable)selfr _inclfiltered __class__s ` r r# z=_install_setup_requires..MinimalDistribution.__init__1 sf 8EEEEESZZ#e**-DEEEH GG X & & & & & ( ( ( ( (r Nc ~ t | \ }}|dfS # t $ r |dfcY S w xY w)zAIgnore ``pyproject.toml``, they are not related to setup_requiresr )r" _split_standard_project_metadata Exception)r& filenamescfgtomlr) s r _get_project_config_fileszN_install_setup_requires..MinimalDistribution._get_project_config_files8 sW
% !GG D DY O O TBw
%
%
% "}$$$
%s '+ <<c dS )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 r N)__name__
__module__ __qualname____doc__r# r0 r2
__classcell__r) s @r MinimalDistributionr + so
) ) ) ) ) % % % % % % r r: T)ignore_option_errors) distutilscorer parse_config_filesr _fetch_build_eggs)r r: dists r _install_setup_requiresrA ( s in 9 6 u % %D 666 $ r c | | j d S # t $ rU}d}d|j j v r?t |d r| | n| 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) r4 hasattrrD announce)r@ exmsgs r r? r? N s d 122222 r| 4 4 4r:&&
, C
l3lll+++
s
A=AA88A=c r t j t | t j j di | S )Nr )r configurerA r< r= r )r s r r r c s8 E""" > ( (% ( ((r c < e Zd ZdZdZ fdZd dZd Zd
dZ 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 t | t | | dS )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 Nc 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 sq dF## ; D&' * * *NC%% &&28&&$$$D
r c 6 t | | }|dS t |t r&t | |t j d| dS t |t rt d |D }nd}|st d|d|d dS )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 V d S r3 )rV rW )r vs r z-Command.ensure_string_list.. s, 99As++999999r FrS z!' must be a list of strings (got )) rT rV rW rU resplitlistallr )r& rX r[ oks r ensure_string_listzCommand.ensure_string_list s dF## ; F
S
!
!
D&"(;"<"< = = = = =#t$$
99S99999
**AGM
r r c t | || }t | | |S r3 )_Commandreinitialize_commandrO rP )r& commandreinit_subcommandsrQ cmds r rj z Command.reinitialize_command s9 ++D';MNN S
r r3 )r )
r4 r5 r6 r7 command_consumes_argumentsr# r\ rg rj r8 r9 s @r r r p s 4 4l "' 6 r r c d t j | d D }t t j j | S )z%
Find all files under 'path'
c 3 h K | ]-\ }}}|D ]$}t j || V %.d S r3 )ospathjoin)r basedirsfilesfiles r r` z#_find_all_simple.. sc D$
T4 r T) followlinks)rq walkfilterrr isfile)rr resultss r _find_all_simpler} sE !#4!@!@!@ G
"'.' * **r c t | }| t j k r5t 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} rq curdir functoolspartialrr relpathmaprd )dirrv make_rels r findallr sR
S ! !E
bi $RW_C@@@He$$ ;;r c N 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 s9 %)
" ""r c e Zd ZdZdS )sicz;Treat this string as-is (https://en.wikipedia.org/wiki/Sic)N)r4 r5 r6 r7 r r r r r s EEEEr r )1r7 r rq rb _distutils_hack.override_distutils_hackdistutils.corer< distutils.errorsr distutils.utilr r r r r _version_moduledependsr discoveryr
r r@ r extensionr
warningsr __all__ __version__bootstrap_install_fromfindr r rA r? r r=
get_unpatchedr ri r} r r wrapsrW r patch_allr r r r sK F F 1 1 1 1 1 1 8 8 8 8 8 8 ( ( ( ( ( ( 9 9 9 9 9 9 9 9 2 2 2 2 2 2 ) "
-2 # # # L *) ) ) $,
6 6 7 7j j j j jh j j jZ + + + # # # F F F F F# F F F
r