o

��
i��@s�dd
lZdd
l
Z
ddlmZmZmZ
ddlmZ
ddl	m
Z

ejdkr*ddlmZ
ner3ddl
mZ
nddlmZ
hd�
ZGd	d
�d
e�ZGdd�de�Zd
S)
�N)�
TYPE_CHECKING�List�Dict)
�build)
�SetuptoolsDeprecationWarning)��)
�Protocol)
�ABC>Z
build_clibZbuild_pyZ
build_scriptsZ	build_extcs*eZ
dZejd
d
�Z�f
dd�Z�ZS)rNc
s:d
d�tj
D�
}
|
trd}t�|t�
tj
|_
t���S)Nc
Ssh|]}
|
d�qS)
r
�)�.0�cmdrr�C/usr/local/lib/python3.10/site-packages/setuptools/command/build.py�	<setcomp>sz)build.get_sub_commands.<locals>.<setcomp>z�
            It seems that you are using `distutils.command.build` to add
            new subcommands. Using `distutils` directly is considered deprecated,
            please use `setuptools.command.build`.
            )�_build�sub_commands�_ORIGINAL_SUBCOMMANDS�warnings�warnr�super�get_sub_commands)�self�subcommands�msg�
�	__class__rrrs





zbuild.get_sub_commands)�__name__�
__module__�__qualname__rrr�
__classcell__rrrrrsrc@s|eZ
dZUd
ZdZeed<	eed<	dd�Zdd�Z	d	d
�Z
deefdd
�Zdeefdd�Z
deeeffdd�ZdS)�
SubCommanda4In order to support editable installations (see :pep:`660`) all
    build subcommands **SHOULD** implement this protocol. They also **MUST** inherit
    from ``setuptools.Command``.

    When creating an :pep:`editable wheel <660>`, ``setuptools`` will try to evaluate
    custom ``build`` subcommands using the following procedure:

    1. ``setuptools`` will set the ``editable_mode`` attribute to ``True``
    2. ``setuptools`` will execute the ``run()`` command.

       .. important::
          Subcommands **SHOULD** take advantage of ``editable_mode=True`` to adequate
          its behaviour or perform optimisations.

          For example, if a subcommand don't need to generate any extra file and
          everything it does is to copy a source file into the build directory,
          ``run()`` **SHOULD** simply "early return".

          Similarly, if the subcommand creates files that would be placed alongside
          Python files in the final distribution, during an editable install
          the command **SHOULD** generate these files "in place" (i.e. write them to
          the original source directory, instead of using the build directory).
          Note that ``get_output_mapping()`` should reflect that and include mappings
          for "in place" builds accordingly.

    3. ``setuptools`` use any knowledge it can derive from the return values of
       ``get_outputs()`` and ``get_output_mapping()`` to create an editable wheel.
       When relevant ``setuptools`` **MAY** attempt to use file links based on the value
       of ``get_output_mapping()``. Alternatively, ``setuptools`` **MAY** attempt to use
       :doc:`import hooks <python:reference/import>` to redirect any attempt to import
       to the directory with the original source code and other files built in place.

    Please note that custom sub-commands **SHOULD NOT** rely on ``run()`` being
    executed (or not) to provide correct return values for ``get_outputs()``,
    ``get_output_mapping()`` or ``get_source_files()``. The ``get_*`` methods should
    work independently of ``run()``.
    F�
editable_modeZ	build_libc


C�d
S�z@(Required by the original :class:`setuptools.Command` interface)Nr�
rrrr�initialize_optionsi�zSubCommand.initialize_optionsc


Cr"r#rr$rrr�finalize_optionslr&zSubCommand.finalize_optionsc


Cr"r#rr$rrr�runor&zSubCommand.run�returnc


Cr")a�

        Return a list of all files that are used by the command to create the expected
        outputs.
        For example, if your build command transpiles Java files into Python, you should
        list here all the Java files.
        The primary purpose of this function is to help populating the ``sdist``
        with all the files necessary to build the distribution.
        All files should be strings relative to the project root directory.
        Nrr$rrr�get_source_filesrr&zSubCommand.get_source_filesc


Cr")a�

        Return a list of files intended for distribution as they would have been
        produced by the build.
        These files should be strings in the form of
        ``"{build_lib}/destination/file/path"``.

        .. note::
           The return value of ``get_output()`` should include all files used as keys
           in ``get_output_mapping()`` plus files that are generated during the build
           and don't correspond to any source file already present in the project.
        Nrr$rrr�get_outputs}r&zSubCommand.get_outputsc


Cr")a�

        Return a mapping between destination files as they would be produced by the
        build (dict keys) into the respective existing (source) files (dict values).
        Existing (source) files should be represented as strings relative to the project
        root directory.
        Destination files should be strings in the form of
        ``"{build_lib}/destination/file/path"``.
        Nrr$rrr�get_output_mapping�r&zSubCommand.get_output_mappingN)rrr�__doc__r!�bool�__annotations__�strr%r'r(rr*r+rr,rrrrr $s

&


r )�sysr�typingrrrZdistutils.command.buildrr�
setuptoolsr�version_infor	Ztyping_extensions�abcr
rr rrrr�<module>
s