Your IP : 18.221.104.12


Current Path : /opt/alt/python313/lib/python3.13/site-packages/setuptools/__pycache__/
Upload File :
Current File : //opt/alt/python313/lib/python3.13/site-packages/setuptools/__pycache__/build_meta.cpython-313.pyc

�

D\Lg�H��8�SrSSKrSSKrSSKrSSKrSSKrSSKrSSKrSSKrSSK	r	SSK
Jr SSKJ
r
JrJrJrJr SSKrSSKrSSKJr SSKJr SSKJr SS	K	Jr SS
KJr /SQr\R<"SS
5R?5r S\ RCSS5;r""SS\#5r$"SS\RJRL5r&\RNS5r(Sr)Sr*Sr+\RNS5r,\\
\-\\-\\-S44r."SS5r/"SS\/5r0"SS\05r1\0"5r2\2Rfr3\2Rhr4\2Rjr5\2Rlr6\2Rnr7\"(d$\2Rpr8\2Rrr9\2Rtr:\1"5r;g) a-A PEP 517 interface to setuptools

Previously, when a user or a command line tool (let's call it a "frontend")
needed to make a request of setuptools to take a certain action, for
example, generating a list of installation requirements, the frontend would
would call "setup.py egg_info" or "setup.py bdist_wheel" on the command line.

PEP 517 defines a different method of interfacing with setuptools. Rather
than calling "setup.py" directly, the frontend should:

  1. Set the current directory to the directory with a setup.py file
  2. Import this module into a safe python interpreter (one in which
     setuptools can potentially set global variables or crash hard).
  3. Call one of the functions defined in PEP 517.

What each function does is defined in PEP 517. However, here is a "casual"
definition of the functions (this definition should not be relied on for
bug reports or API stability):

  - `build_wheel`: build a wheel in the folder and return the basename
  - `get_requires_for_build_wheel`: get the `setup_requires` to build
  - `prepare_metadata_for_build_wheel`: get the `install_requires`
  - `build_sdist`: build an sdist in the folder and return the basename
  - `get_requires_for_build_sdist`: get the `setup_requires` to build

Again, this is not a formal definition! Just a "taste" of the module.
�N)�Path)�Dict�Iterator�List�Optional�Union�)�errors)�	same_path)�
parse_strings)�SetuptoolsDeprecationWarning)�	strtobool)
�get_requires_for_build_sdist�get_requires_for_build_wheel� prepare_metadata_for_build_wheel�build_wheel�build_sdist�get_requires_for_build_editable�#prepare_metadata_for_build_editable�build_editable�
__legacy__�SetupRequirementsError�SETUPTOOLS_ENABLE_FEATURES�zlegacy-editable�_�-c��\rSrSrSrSrg)r�Cc��Xlg�N��
specifiers)�selfr"s  ڎ/builddir/build/BUILDROOT/alt-python313-setuptools-69.0.2-1.el8.x86_64/opt/alt/python313/lib/python3.13/site-packages/setuptools/build_meta.py�__init__�SetupRequirementsError.__init__Ds��$��r!N)�__name__�
__module__�__qualname__�__firstlineno__r%�__static_attributes__�r'r$rrCs��%r'rc�H�\rSrSrSr\\RS55rSr	g)�Distribution�Hc�@�[[U55n[U5er )�listrr)r#r"�specifier_lists   r$�fetch_build_eggs�Distribution.fetch_build_eggsIs���m�J�7�8��$�^�4�4r'c#��# �[RRnU[RlSv� U[Rlg!U[Rlf=f7f)zW
Replace
distutils.dist.Distribution with this class
for the duration of this context.
N)�	distutils�corer/)�cls�origs  r$�patch�Distribution.patchNsB����~�~�*�*��&)�	���#�	/��*.�I�N�N�'��$�I�N�N�'�s�0A'�A
�A'�
A$�$A'r-N)
r(r)r*r+r4�classmethod�
contextlib�contextmanagerr;r,r-r'r$r/r/Hs)��5�
����/���/r'r/c#�# �[RnS[lSv� U[lg!U[lf=f7f)z�Temporarily disable installing setup_requires

Under PEP 517, the backend reports build dependencies to the frontend,
and the frontend is responsible for ensuring they're installed.
So setuptools (acting as a backend) should not try to install them.
c��gr r-)�attrss r$�<lambda>�+no_install_setup_requires.<locals>.<lambda>gs��tr'N)�
setuptools�_install_setup_requires)r:s r$�no_install_setup_requiresrG^s2����-�-�D�);�J�&�2�
�-1�
�*��T�
�*�s�A�0�A�
=�Ac	���[R"U5Vs/sHHn[RR[RR	X55(dMFUPMJ sn$s snfr )�os�listdir�path�isdir�join)�a_dir�names  r$�_get_immediate_subdirectoriesrPnsI�����E�*��*��b�g�g�m�m�B�G�G�L�L��<U�.V��*����s�AA*�!A*c�^�U4Sj[R"U55nUunU$![a [S5ef=f)Nc3�T># �UHoRT5(dMUv� M  g7fr )�endswith)�.0�f�	extensions  �r$�	<genexpr>�'_file_with_extension.<locals>.<genexpr>us����J�0�a�J�J�y�4I���0�s�(�	(z[No distribution was found. Ensure that `setup.py` is not empty and that it calls `setup()`.)rIrJ�
ValueError)�	directoryrV�matching�files `  r$�_file_with_extensionr]tsL���J�2�:�:�i�0�J�H�
�����K���
��
8�
�	
�
�s�)�?c��[RRU5(d[R"S5$[[S[5"U5$)Nz%from setuptools import setup; setup()�open)rIrK�exists�io�StringIO�getattr�tokenizer_��setup_scripts r$�_open_setup_scriptrg�s9��
�7�7�>�>�,�'�'��{�{�C�D�D��8�V�T�*�<�8�8r'c#�# �[R"5 [R"SS5 Sv� SSS5 g!,(df   g=f7f)N�ignorezsetup.py install is deprecated)�warnings�catch_warnings�filterwarningsr-r'r$�suppress_known_deprecationrm�s0���	�	 �	 �	"�����*J�K�
�
#�	"�	"�s�A�=�	A�
A�Ac��\rSrSrSrS\S\S\\4SjrS\S\	\4Sjr
S\S\	\4SjrS\S\	\4S	jrS\S\	\4S
jr
Srg)
�_ConfigSettingsTranslator�zTranslate ``config_settings`` into distutils-style command arguments.
Only a limited number of options is currently supported.
�key�config_settings�returnc��U=(d 0nURU5=(d /n[U[5(a[R"U5$U$)a�
Get the value of a specific key in ``config_settings`` as a list of strings.

>>> fn = _ConfigSettingsTranslator()._get_config
>>> fn("--global-option", None)
[]
>>> fn("--global-option", {})
[]
>>> fn("--global-option", {'--global-option': 'foo'})
['foo']
>>> fn("--global-option", {'--global-option': ['foo']})
['foo']
>>> fn("--global-option", {'--global-option': 'foo'})
['foo']
>>> fn("--global-option", {'--global-option': 'foo bar'})
['foo', 'bar']
)�get�
isinstance�str�shlex�split)r#rqrr�cfg�optss     r$�_get_config�%_ConfigSettingsTranslator._get_config�s@��$�#����w�w�s�|�!�r��$.�t�S�$9�$9�u�{�{�4� �C�t�Cr'c#��# �U=(d 0n1SknSU;dSU;aU[URS5=(d URS5=(d S5nUR5U;aSOSv� SU;dSU;aU[URS5=(d URS5=(d S5nUR5U;aSOSv� URS	U5S
hv�N g
N7f)a
Let the user specify ``verbose`` or ``quiet`` + escape hatch via
``--global-option``.
Note: ``-v``, ``-vv``, ``-vvv`` have similar effects in setuptools,
so we just have to cover the basic scenario ``-v``.

>>> fn = _ConfigSettingsTranslator()._global_args
>>> list(fn(None))
[]
>>> list(fn({"verbose": "False"}))
['-q']
>>> list(fn({"verbose": "1"}))
['-v']
>>> list(fn({"--verbose": None}))
['-v']
>>> list(fn({"verbose": "true", "--global-option": "-q --no-user-cfg"}))
['-v', '-q', '--no-user-cfg']
>>> list(fn({"--quiet": None}))
['-q']
>�0�no�off�false�verbosez	--verbose�1z-qz-v�quietz--quietz--global-optionN)rwru�lowerr|)r#rrrz�falsey�levels     r$�_global_args�&_ConfigSettingsTranslator._global_args�s����*�#���,�����{�c�1�����	�*�I�c�g�g�k�.B�I�c�J�E� �;�;�=�F�2�4��=��c�>�Y�#�-������(�E�C�G�G�I�,>�E�#�F�E� �;�;�=�F�2�4��=��#�#�$5��G�G�G�s�C'C1�)C/�*C1c#��# �U=(d 0nSU;a-[[US=(d S55nU(aSOSv� SU;aS[US5/Shv�N ggN7f)aH
The ``dist_info`` command accepts ``tag-date`` and ``tag-build``.

.. warning::
   We cannot use this yet as it requires the ``sdist`` and ``bdist_wheel``
   commands run in ``build_sdist`` and ``build_wheel`` to reuse the egg-info
   directory created in ``prepare_metadata_for_build_wheel``.

>>> fn = _ConfigSettingsTranslator()._ConfigSettingsTranslator__dist_info_args
>>> list(fn(None))
[]
>>> list(fn({"tag-date": "False"}))
['--no-date']
>>> list(fn({"tag-date": None}))
['--no-date']
>>> list(fn({"tag-date": "true", "tag-build": ".a"}))
['--tag-date', '--tag-build', '.a']
ztag-dater�z
--tag-datez	--no-datez	tag-buildz--tag-buildN)rrw)r#rrrz�vals    r$�__dist_info_args�*_ConfigSettingsTranslator.__dist_info_args�sc���&�#�������C��J�� :�7�;�<�C�#&�<�K�8��#��%�s�3�{�+;�'<�=�=�=��=�s�AA#�A!�A#c#�# �U=(d 0nURS5=(d URS5nU(dgS[U5/Shv�N gN7f)z�
The ``editable_wheel`` command accepts ``editable-mode=strict``.

>>> fn = _ConfigSettingsTranslator()._editable_args
>>> list(fn(None))
[]
>>> list(fn({"editable-mode": "strict"}))
['--mode', 'strict']
z
editable-mode�
editable_modeNz--mode)rurw)r#rrrz�modes    r$�_editable_args�(_ConfigSettingsTranslator._editable_args�sE����#����w�w��'�C�3�7�7�?�+C�����c�$�i�(�(�(�s�A
A�A�Ac#�D# �URSU5Shv�N gN7f)a�
Users may expect to pass arbitrary lists of arguments to a command
via "--global-option" (example provided in PEP 517 of a "escape hatch").

>>> fn = _ConfigSettingsTranslator()._arbitrary_args
>>> list(fn(None))
[]
>>> list(fn({}))
[]
>>> list(fn({'--build-option': 'foo'}))
['foo']
>>> list(fn({'--build-option': ['foo']}))
['foo']
>>> list(fn({'--build-option': 'foo'}))
['foo']
>>> list(fn({'--build-option': 'foo bar'}))
['foo', 'bar']
>>> list(fn({'--global-option': 'foo'}))
[]
z--build-optionN)r|�r#rrs  r$�_arbitrary_args�)_ConfigSettingsTranslator._arbitrary_argss���*�#�#�$4�o�F�F�F�s� �� r-N)r(r)r*r+�__doc__rw�_ConfigSettingsrr|rr��)_ConfigSettingsTranslator__dist_info_argsr�r�r,r-r'r$roro�s����D�s�D�_�D��c��D�,H�O�H���
�H�@>��>�H�S�M�>�4)�o�)�(�3�-�)� G��G�8�C�=�Gr'roc���\rSrSrSrSSjrSSjrSSjrS\S\S	\4S
jr	S\S\S	\
4SjrSSjrS
r
SSjrSSjrS\\S	\\4Sjr\(dSSjrSSjrSSjrSrgSrg)�_BuildMetaBackendic�4�/[RSSQURU5QSP[l[R	5 UR5 SSS5 U$!,(df   U$=f![anX#R-
nSnAU$SnAff=f)Nr	�egg_info)�sys�argvr�r/r;�	run_setuprr")r#rr�requirements�es    r$�_get_build_requires�%_BuildMetaBackend._get_build_requiress���
�
�X�X�b�q�\�
�
�
�
��
/�
�
�
���
	)��#�#�%���� �&�
��&�%�
���&�	)��L�L�(�L����	)�s5�A4�A"�A4�"
A1�,A4�1A4�4
B�>B�Bc�x�[RRU5nSn[U5nUR	5RSS5nSSS5 [
W[55 g!,(df   N$=f![a2nUR(ae[R"SSSS9 SnAgSnAff=f)N�__main__z\r\nz\nz6Running `setup.py` directly as CLI tool is deprecated.znPlease avoid using `sys.exit(0)` or similar statements that don't fit in the paradigm of a configuration file.zAhttps://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html)�see_url)rIrK�abspathrg�read�replace�exec�locals�
SystemExit�coder
�emit)r#rf�__file__r(rUr�r�s       r$r��_BuildMetaBackend.run_setup-s����7�7�?�?�<�0����
��
)�Q��6�6�8�#�#�G�U�3�D�*�	���v�x� �	*�
)��
�
	��v�v��(�-�-�H�J�+�	
��	
	�s#�!A,�A=�,
A:�=
B9�(B4�4B9Nc�$�URUS/S9$)N�wheel�r��r�r�s  r$r�._BuildMetaBackend.get_requires_for_build_wheelDs���'�'��w�i�'�P�Pr'c�"�URU/S9$)Nr�r�r�s  r$r�._BuildMetaBackend.get_requires_for_build_sdistGs���'�'��b�'�I�Ir'�metadata_directory�suffixrsc��URX5n[URU5(d [R"[U5U5 UR$)z�
PEP 517 requires that the .dist-info directory be placed in the
metadata_directory. To comply, we MUST copy the directory to the root.

Returns the basename of the info directory, e.g. `proj-0.0.0.dist-info`.
)�_find_info_directoryr�parent�shutil�moverwrO)r#r�r��info_dirs    r$�_bubble_up_info_directory�+_BuildMetaBackend._bubble_up_info_directoryJsD���,�,�-?�H������*<�=�=��K�K��H�
�'9�:��}�}�r'c�h�[R"U5Hvup4nUVs/sHofRU5(dMUPM nn[U5S:wd[U5S:wdMN[U5S:XdSUS35e[	X7S5s $ SUSU3n[
R"U5es snf)Nrr	z	Multiple z directories foundzNo z directory found in )rI�walkrS�lenrr
�
InternalError)	r#r�r�r��dirsrrU�
candidates�msgs	         r$r��&_BuildMetaBackend._find_info_directoryWs���!�w�w�'9�:�O�F�!�%)�@�T��Z�Z��-?�!�T�J�@��:��!�#�s�4�y�A�~��:��!�+�S�y���@R�-S�S�+��F�q�M�2�2� ;��F�8�/�0B�/C�D���"�"�3�'�'��As
�B/�B/c� �/[RSSQURU5QSPSPUPSP[l[5 UR	5 SSS5 URUS5 URUS5$!,(df   N2=f)Nr	�	dist_infoz--output-dirz--keep-egg-infoz	.egg-infoz
.dist-info)r�r�r�rGr�r��r#r�rrs   r$r�2_BuildMetaBackend.prepare_metadata_for_build_wheelbs���
�
�X�X�b�q�\�
�
�
�
��
/�
�
�
�
�	
�

�
�
�

���'�
(��N�N��)�	
�&�&�'9�;�G��-�-�.@�,�O�O�	)�
(�s�A?�?
B
c���[RRU5n[R"USS9 SUS.n[R
"S0UD6n/[RSSQURU5QUQSPUP[l[5 UR5 SSS5 [Xb5n[RRX75n[RRU5(a[R"U5 [R"[RRXg5U5 SSS5 U$!,(df   N�=f!,(df   W$=f)NT)�exist_okz.tmp-)�prefix�dirr	z
--dist-dirr-)rIrKr��makedirs�tempfile�TemporaryDirectoryr�r�r�rGr�r]rMr`�remove�rename)	r#�
setup_command�result_extension�result_directoryrr�	temp_opts�tmp_dist_dir�result_basename�result_paths	         r$�_build_with_temp_dir�&_BuildMetaBackend._build_with_temp_dirss*���7�7�?�?�+;�<��	���$�t�4�&�/?�@�	�
�
(�
(�
5�9�
5������"�1����"�"�?�3�����	�
��C�H�+�,���� �-�3�<�R�O��'�'�,�,�'7�I�K��w�w�~�~�k�*�*��	�	�+�&��I�I�b�g�g�l�l�<�A�;�O�!6�$��-�,��6�
5�$��s&�AE�E�!B E�
E	�E�
E+c��[5 URS/URU5QSUU5sSSS5 $!,(df   g=f)N�bdist_wheel�.whl)rmr�r�)r#�wheel_directoryrrr�s    r$r�_BuildMetaBackend.build_wheel�sC��(�
)��,�,��G��!5�!5�o�!F�G����	�*�
)�
)�s	�&;�
A	c�,�UR/SQSX5$)N)�sdistz	--formats�gztarz.tar.gz)r�)r#�sdist_directoryrrs   r$r�_BuildMetaBackend.build_sdist�s���(�(�+�Y��
�	
r'c��U(dg[[U5RS55n[U5S::deU(a[	US5$S$)Nz*.dist-infor	r)r2r�globr�rw)r#r��dist_info_candidatess   r$�_get_dist_info_dir�$_BuildMetaBackend._get_dist_info_dir�sP��!��#�D�);�$<�$A�$A�-�$P�Q���'�(�A�-�-�-�/C�s�'��*�+�M��Mr'c���URU5nU(aSU/O/nS/UQURU5Qn[5 URUSX5sSSS5 $!,(df   g=f)Nz--dist-info-dir�editable_wheelr�)r�r�rmr�)r#r�rrr�r�r{�cmds       r$r� _BuildMetaBackend.build_editable�sh���.�.�/A�B�H�4<�%�x�0�"�D�#�R�d�R�T�-@�-@��-Q�R�C�+�-��0�0�����.�-�-�s�A�
A*c�$�URU5$r )rr�s  r$r�1_BuildMetaBackend.get_requires_for_build_editable�s���4�4�_�E�Er'c�$�URX5$r )rr�s   r$r�5_BuildMetaBackend.prepare_metadata_for_build_editable�s���8�8�"��
r'r-�zsetup.pyr )NN)r(r)r*r+r�r�rrrwr�rr�rr�rrrr��LEGACY_EDITABLErrrr,r-r'r$r�r�s�����.Q�J��C����QT��	(�s�	(�C�	(�D�	(�37�P�"�<IM�	�
�
N�X�c�]�N�x�PS�}�N��MQ�
	�	F�7;�	�)r'r�c�0^�\rSrSrSrSU4SjjrSrU=r$)�_BuildMetaLegacyBackendi�a/Compatibility backend for setuptools

This is a version of setuptools.build_meta that endeavors
to maintain backwards
compatibility with pre-PEP 517 modes of invocation. It
exists as a temporary
bridge between the old packaging mechanism and the new
packaging mechanism,
and will eventually be removed.
c�*>�[[R5n[RR	[RRU55nU[R;a [RR
SU5 [RSnU[RS'[[U]+US9 U[RSS&U[RS'g!U[RSS&U[RS'f=f)Nrre)r2r�rKrI�dirnamer��insertr��superr�r�)r#rf�sys_path�
script_dir�
sys_argv_0�	__class__s     �r$r��!_BuildMetaLegacyBackend.run_setup�s��������>���W�W�_�_�R�W�W�_�_�\�%B�C�
��S�X�X�%��H�H�O�O�A�z�*�
�X�X�a�[�
�"������		%��)�4�:��:�U�#�C�H�H�Q�K�$�C�H�H�Q�K��#�C�H�H�Q�K�$�C�H�H�Q�K�s�2C*�*(Dr-r�)r(r)r*r+r�r�r,�
__classcell__)rs@r$r�r��s���	�%�%r'r�)<r�rarIrxr�rdr�r>r�rj�pathlibr�typingrrrrrrEr7rr
�_pathr�_reqsrr
�distutils.utilr�__all__�getenvr�rr�r��
BaseExceptionr�distr/r?rGrPr]rgrmrwr�ror�r��_BACKENDrrrrrrrrrr-r'r$�<module>rs����8
�	��
��
�����8�8����� �2�$��� �Y�Y�'C�R�H�N�N�P��#�'A�'I�'I�#�s�'S�S��%�]�%�
/�:�?�?�/�/�/�,���2��2��	�9��������4��U�3��S�	�4�+?�%@� @�A�B���|G�|G�~b�1�b�J%%�/�%%�R���'�D�D��'�D�D��#+�#L�#L� ��"�"���"�"���&.�&N�&N�#�*2�*V�*V�'��,�,�N�%�
&�
r'

?>