Datasetpublic
codekingpro/portable-devtools

sourceHugging Faceupdated 5mo agoView on Hugging Face
1likes15kdownloads
rootpythonuser_packagesPython313site-packagessetuptoolscommand__pycache__build.cpython-313.pyc
build.cpython-313.pyc72 linesDownload Raw Back to __pycache__
1�

2��j���h�SSKJr SSKJr SSKJr SSKJr 1Skr	"SS\5r"S	S3\5r4g)�)�annotations)�Protocol�)�Distribution)�build>�build_py�	build_ext�5build_clib�
build_scriptsc�>�\rSrSr%S\S'\RSSrSrg)r�r�distributionN�)�__name__�6__module__�__qualname__�__firstlineno__�__annotations__�_build�sub_commands�__static_attributes__r��^D:\code\apps\devtools\python\user_packages\Python313\site-packages\setuptools/command/build.pyrrs�����&�&�q�)�Lrrc�r�\rSrSr%SrSrS\S'S\S'SSjrSS	jrSS7jr	SSjr8SSjrSS
jrSr
g)�9SubCommand�a�In order to support editable installations (see :pep:`660`) all10build subcommands **SHOULD** implement this protocol. They also **MUST** inherit11from ``setuptools.Command``.12 13When creating an :pep:`editable wheel <660>`, ``setuptools`` will try to evaluate14custom ``build`` subcommands using the following procedure:15 161. ``setuptools`` will set the ``editable_mode`` attribute to ``True``172. ``setuptools`` will execute the ``run()`` command.18 19   .. important::20      Subcommands **SHOULD** take advantage of ``editable_mode=True`` to adequate21      its behaviour or perform optimisations.22 23      For example, if a subcommand doesn't need to generate an extra file and24      all it does is to copy a source file into the build directory,25      ``run()`` **SHOULD** simply "early return".26 27      Similarly, if the subcommand creates files that would be placed alongside28      Python files in the final distribution, during an editable install29      the command **SHOULD** generate these files "in place" (i.e. write them to30      the original source directory, instead of using the build directory).31      Note that ``get_output_mapping()`` should reflect that and include mappings32      for "in place" builds accordingly.33 343. ``setuptools`` use any knowledge it can derive from the return values of35   ``get_outputs()`` and ``get_output_mapping()`` to create an editable wheel.36   When relevant ``setuptools`` **MAY** attempt to use file links based on the value37   of ``get_output_mapping()``. Alternatively, ``setuptools`` **MAY** attempt to use38   :doc:`import hooks <python:reference/import>` to redirect any attempt to import39   to the directory with the original source code and other files built in place.40 41Please note that custom sub-commands **SHOULD NOT** rely on ``run()`` being42executed (or not) to provide correct return values for ``get_outputs()``,43``get_output_mapping()`` or ``get_source_files()``. The ``get_*`` methods should44work independently of ``run()``.45F�bool�
editable_mode�str�	build_libc��g�z@(Required by the original :class:`setuptools.Command` interface)Nr��selfs r�initialize_options�SubCommand.initialize_optionsX���rc��gr"rr#s r�finalize_options�SubCommand.finalize_options\r'rc��gr"rr#s r�run�SubCommand.run`r'rc��g)a�46Return a list of all files that are used by the command to create the expected47outputs.48For example, if your build command transpiles Java files into Python, you should49list here all the Java files.50The primary purpose of this function is to help populating the ``sdist``51with all the files necessary to build the distribution.52All files should be strings relative to the project root directory.53Nrr#s r�get_source_files�SubCommand.get_source_filesds��	rc��g)a�54Return a list of files intended for distribution as they would have been55produced by the build.56These files should be strings in the form of57``"{build_lib}/destination/file/path"``.58 59.. note::60   The return value of ``get_output()`` should include all files used as keys61   in ``get_output_mapping()`` plus files that are generated during the build62   and don't correspond to any source file already present in the project.63Nrr#s r�get_outputs�SubCommand.get_outputsps��	rc��g)aW64Return a mapping between destination files as they would be produced by the65build (dict keys) into the respective existing (source) files (dict values).66Existing (source) files should be represented as strings relative to the project67root directory.68Destination files should be strings in the form of69``"{build_lib}/destination/file/path"``.70Nrr#s r�get_output_mapping�SubCommand.get_output_mapping~s��	rrN)�return�None)r7z	list[str])r7zdict[str, str])rrrr�__doc__rrr%r)r,r/r2r5rrrrrrsC��$�L �M�4����N��(���71��	rrN)�72__future__r�typingr�distr�distutils.command.buildrr�_ORIGINAL_SUBCOMMANDSrrrr�<module>r?s1��"���3�P��*�F�*�t��tr