_i d dl Z d dlmZmZmZ d dlmZ ddlm Z e j dk\ rd dlm Z nerd dl m Z nd dl
mZ h d Z G d
d e Z G d d
e Zy) N)
TYPE_CHECKINGListDict)build ) SetuptoolsDeprecationWarning) )Protocol)ABC> build_py build_ext
build_clib
build_scriptsc < e Zd Zej dd Z fdZ xZS )r Nc t j D ch c] }|d }}|t z
r.t j dddd t j | _ t
| S c c}w )Nr z$Direct usage of `distutils` commandsz
It seems that you are using `distutils.command.build` to add
new subcommands. Using `distutils` directly is considered deprecated,
please use `setuptools.command.build`.
)i
z!https://peps.python.org/pep-0632/)due_datesee_url)_build sub_commands_ORIGINAL_SUBCOMMANDSr emitsuperget_sub_commands)selfcmd subcommands __class__s /builddir/build/BUILDROOT/alt-python312-setuptools-69.0.2-3.el8.x86_64/opt/alt/python312/lib/python3.12/site-packages/setuptools/command/build.pyr zbuild.get_sub_commands sm )/)<)<=)<#s1v)< = . . ( - -6
(;
!' 3 3D w')) >s A')__name__
__module__ __qualname__r r r
__classcell__)r s @r! r r s &&q)L* * r c z e Zd ZU dZdZeed< eed< d Zd Z d Z
de e fd Z de e fd
Z
deeef fd Zy )
SubCommanda. In 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 doesn't need to generate an extra file and
all 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 ` 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_mode build_libc yz@(Required by the original :class:`setuptools.Command` interface)N r s r! initialize_optionsz SubCommand.initialize_optionsl r& c yr, r- r. s r! finalize_optionszSubCommand.finalize_optionso r0 r& c yr, r- r. s r! runzSubCommand.runr r0 r& returnc y)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.
Nr- r. s r! get_source_fileszSubCommand.get_source_filesu r0 r& c y)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.
Nr- r. s r! get_outputszSubCommand.get_outputs r0 r& c y)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"``.
Nr- r. s r! get_output_mappingz SubCommand.get_output_mapping r0 r& N)r" r# r$ __doc__r) bool__annotations__strr/ r2 r4 r r7 r9 r r; r- r& r! r( r( ' sk $L M4 N(OOO $s) T#Y DcN r& r( )systypingr r r distutils.command.buildr r warningsr version_infor typing_extensionsabcr r r( r- r& r! rG sQ
, , 3 3v *# Q *F **n n r&