File: //opt/saltstack/salt/lib/python3.10/site-packages/setuptools/__pycache__/build_meta.cpython-310.pyc
o
;j
O � @ s� U d Z ddlmZ ddlZddlZddlZddlZddlZddlZddl Z ddl
Z
ddl Z ddl m
Z
mZmZ ddlmZ ddlmZmZmZ ddlZddlmZ dd lmZmZ dd
l m Z dd l m Z ddl Z dd l m!Z! erwdd
l"m#Z# g d�Z$G dd� de%�Z&G dd� dej'j(�Z(ej)dd� �Z*dd� Z+d+dd �Z,d d � Z-ej)d d � �Z.eee/ee/e0e/ df f df Z1d!e2d"< G d#d$� d$�Z3G d%d&� d&e3�Z4G d'd(� d(e4�Z5G d)d*� d*e �Z6e4� Z7e7j8Z8e7j9Z9e7j:Z:e7j;Z;e7j<Z<e7j=Z=e7j>Z>e7j?Z?e5� Z@dS ),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 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.
� )� annotationsN)�Iterable�Iterator�Mapping)�Path)�
TYPE_CHECKING�NoReturn�Union� )�errors)�StrPath� same_path)�
parse_strings)� SetuptoolsDeprecationWarning)� strtobool)� TypeAlias)
� 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__�SetupRequirementsErrorc @ s e Zd Zddd�ZdS )r �return�Nonec C s
|| _ d S �N)�
specifiers)�selfr � r! �I/opt/saltstack/salt/lib/python3.10/site-packages/setuptools/build_meta.py�__init__H s
z SetupRequirementsError.__init__N)r r )�__name__�
__module__� __qualname__r# r! r! r! r" r G s r c @ s* e Zd Zd dd�Zeejd
dd���ZdS ) � Distributionr r c C s t t|��}t|��r )�listr r )r r Zspecifier_listr! r! r" �fetch_build_eggsM s z Distribution.fetch_build_eggs�Iterator[None]c c s2 � t jj}| t j_z
dV W |t j_dS |t j_w )zw
Replace
distutils.dist.Distribution with this class
for the duration of this context.
N)� distutils�corer' )�cls�origr! r! r" �patchR s �zDistribution.patchN)r r )r r* )r$ r% r& r) � classmethod�
contextlib�contextmanagerr/ r! r! r! r" r' L s
r' c c s. � t j} dd� t _z dV W | t _dS | t _w )a
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 S s d S r r! )�attrsr! r! r" �<lambda>k s z+no_install_setup_requires.<locals>.<lambda>N)�
setuptoolsZ_install_setup_requires)r. r! r! r" �no_install_setup_requiresb s �
r6 c s � fdd�t �� �D �S )Nc s& g | ]}t j�t j�� |��r|�qS r! )�os�path�isdir�join)�.0�name�Za_dirr! r" �
<listcomp>s s
��z1_get_immediate_subdirectories.<locals>.<listcomp>)r7 �listdirr= r! r= r" � _get_immediate_subdirectoriesr s
�r@ � directoryr � extension�str | tuple[str, ...]c s> � fdd�t �| �D �}z|\}W |S ty td�d �w )Nc 3 s � | ]
}|� � �r|V qd S r ��endswith�r; �f�rB r! r" � <genexpr>y s � z'_file_with_extension.<locals>.<genexpr>z[No distribution was found. Ensure that `setup.py` is not empty and that it calls `setup()`.)r7 r? �
ValueError)rA rB Zmatching�filer! rH r" �_file_with_extensionx s ����rL c C s t j�| �s t�d�S t�| �S )Nz%from setuptools import setup; setup())r7 r8 �exists�io�StringIO�tokenize�open�� setup_scriptr! r! r" �_open_setup_script� s
rT c c sB � t �� � t �dd� d V W d � d S 1 sw Y d S )N�ignorez setup.py install is deprecated)�warnings�catch_warnings�filterwarningsr! r! r! r" �suppress_known_deprecation� s
�
"�rY r �_ConfigSettingsc @ sB e Zd ZdZddd �Zdd d �Zdd
d�Zddd�Zddd�ZdS )�_ConfigSettingsTranslatorz�Translate ``config_settings`` into distutils-style command arguments.
Only a limited number of options is currently supported.
�key�str�config_settingsrZ r � list[str]c C s. |pi }|� |�p
g }t|t�rt�|�S |S )aA
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�
isinstancer] �shlex�split)r r\ r^ �cfg�optsr! r! r" � _get_config� s z%_ConfigSettingsTranslator._get_config�
Iterator[str]c c s� � |pi }h d�}d|v sd|v r*t |�d�p |�d�p d�}|�� |v r'dndV d|v s2d|v rKt |�d�p>|�d�p>d�}|�� |v rHdndV | �d |�E d
H d
S ) 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']
> �false�0Zoff�no�verbosez --verbose�1z-qz-v�quietz--quietz--global-optionN)r] r` �lowerrf )r r^ rd Zfalsey�levelr! r! r" � _global_args� s � z&_ConfigSettingsTranslator._global_argsc c sZ � |pi }d|v rt t|d pd��}|rdndV d|v r+dt|d �gE dH dS dS )a�
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-daterh z
--tag-datez --no-datez tag-buildz --tag-buildN)r r] )r r^ rd �valr! r! r" Z__dist_info_args� s ��z*_ConfigSettingsTranslator.__dist_info_argsc c s< � |pi }|� d�p|� d�}|sdS dt|�gE dH dS )a
The ``editable_wheel`` command accepts ``editable-mode=strict``.
>>> fn = _ConfigSettingsTranslator()._editable_args
>>> list(fn(None))
[]
>>> list(fn({"editable-mode": "strict"}))
['--mode', 'strict']
z
editable-modeZ
editable_modeNz--mode)r` r] )r r^ rd �moder! r! r" �_editable_args� s �
z(_ConfigSettingsTranslator._editable_argsc c s � | � d|�E dH dS )av
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)rf �r r^ r! r! r" �_arbitrary_args
s �z)_ConfigSettingsTranslator._arbitrary_argsN)r\ r] r^ rZ r r_ )r^ rZ r rg ) r$ r% r& �__doc__rf rp Z)_ConfigSettingsTranslator__dist_info_argsrs ru r! r! r! r" r[ � s
r[ c @ s� e Zd Zd6dd�Zd7d8d d
�Z d9d:dd�Z d9d:dd�Zd;dd�Zd<dd�Z d9d=dd �Z d>d?d$d%�Z
d@dAd(d)�Z d9dBd+d,�Z dCd.d/�Z
d@dAd0d1�Z d9d:d2d3�Z d9d=d4d5�ZdS )D�_BuildMetaBackendr^ rZ � requirementsr_ c
C s� g t jd d� �| �|��d�t _z t�� � | �� W d � W |S 1 s'w Y W |S tyF } z ||j7 }W Y d }~|S d }~ww )Nr
Zegg_info)�sys�argvrp r' r/ � run_setupr r )r r^ rx �er! r! r" �_get_build_requires# s& ���
�����z%_BuildMetaBackend._get_build_requires�setup.pyrS r] r r c
C s� t j�|�}d}t|��}|�� �dd�}W d � n1 s w Y z t|t� � W d S tyL } z|j r9� t
j dddd� W Y d }~d S d }~ww )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)Zsee_url) r7 r8 �abspathrT �read�replace�exec�locals�
SystemExit�coder �emit)r rS �__file__r$ rG r� r| r! r! r" r{ 3 s"
����z_BuildMetaBackend.run_setupNc C � | j |g d�S �N)rx �r} rt r! r! r" r J � z._BuildMetaBackend.get_requires_for_build_wheelc C r� r� r� rt r! r! r" r O r� z._BuildMetaBackend.get_requires_for_build_sdist�metadata_directoryr �suffixc C s. | � ||�}t|j|�st�t|�|� |jS )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�mover] r< )r r� r� �info_dirr! r! r" �_bubble_up_info_directoryT s z+_BuildMetaBackend._bubble_up_info_directoryr c s� t �|�D ]8\}}}� fdd�|D �}t|�dks t|�dkr=t|�dks4J d� � dt|�� d|� ���t||d � S qd� � d |� �}t�|��)
Nc s g | ] }|� � �r|�qS r! rD rF �r� r! r" r> e s z:_BuildMetaBackend._find_info_directory.<locals>.<listcomp>r r
z Exactly one z& should have been produced, but found z: zNo z directory found in )r7 �walk�lenr r Z
InternalError)r r� r� r� �dirs�_Z
candidates�msgr! r� r" r� c s ��
z&_BuildMetaBackend._find_info_directoryc C sx g t jd d� �| �|��d�d�t|��d�t _t� � | �� W d � n1 s+w Y | �|d� | �|d�S )Nr
Z dist_infoz --output-dirz--keep-egg-infoz .egg-infoz
.dist-info)ry rz rp r] r6 r{ r� �r r� r^ r! r! r" r p s$ ������
� z2_BuildMetaBackend.prepare_metadata_for_build_wheelr! �
setup_command�
Iterable[str]�result_extensionrC �result_directory�arbitrary_argsc C s� t j�|�}t j|dd� tjd|d��Y}g tjd d� �| �|��|�d�|�|�t_t � � | �
� W d � n1 s>w Y t ||�}t j� ||�}t j�
|�rZt �|� t �t j� ||�|� W d � |S 1 spw Y |S )NT)�exist_okz.tmp-)�prefix�dirr
z
--dist-dir)r7 r8 r� �makedirs�tempfileZTemporaryDirectoryry rz rp r6 r{ rL r: rM �remove�rename) r r� r� r� r^ r� Z tmp_dist_dirZresult_basename� result_pathr! r! r" �_build_with_temp_dir� s> � ������
�
��z&_BuildMetaBackend._build_with_temp_dir�wheel_directory�StrPath | Nonec
s~ d� ��fdd� }|d u r|dg�S z
|ddt |�g�W S ty> } zdt |�vr+� t�� |dg�W Y d }~S d }~ww ) N�cmdr_ c
sB t � � ��| d�� ��� ��W d � S 1 sw Y d S )N�.whl)rY r� ru )r� �r^ r r� r! r" �_build� s �$�z-_BuildMetaBackend.build_wheel.<locals>._buildZ bdist_wheel�--dist-info-dirz --dist-info-dir not recognized)r� r_ )r] r� �_IncompatibleBdistWheelr� )r r� r^ r� r� �exr! r� r" r � s
��z _BuildMetaBackend.build_wheel�sdist_directoryc C s | � g d�d||�S )N)Zsdistz --formats�gztarz.tar.gz)r� )r r� r^ r! r! r" r � s �z _BuildMetaBackend.build_sdist�
str | Nonec C s> |sd S t t|��d��}t|�dksJ �|r t|d �S d S )Nz *.dist-infor
r )r( r �globr� r] )r r� Zdist_info_candidatesr! r! r" �_get_dist_info_dir� s
z$_BuildMetaBackend._get_dist_info_dirc C sh | � |�}|r d|gng }dg|�| �|��}t� � | �|d||�W d � S 1 s-w Y d S )Nr� Zeditable_wheelr� )r� rs rY r� )r r� r^ r� r� re r� r! r! r" r � s
�$�z _BuildMetaBackend.build_editablec C s
| � |�S r )r rt r! r! r" r � s
z1_BuildMetaBackend.get_requires_for_build_editablec C s | � ||�S r )r r� r! r! r" r � s �z5_BuildMetaBackend.prepare_metadata_for_build_editable)r^ rZ rx r_ �r~ �rS r] r r r )r^ rZ r r_ )r� r r� r] r r] )r� r r� r] r r )r� r r^ rZ r r] )r! )
r� r� r� rC r� r r^ rZ r� r� )NN)r� r r^ rZ r� r� r r] )r� r r^ rZ r r] )r� r� r r� )r$ r% r& r} r{ r r r� r� r r� r r r� r r r r! r! r! r" rw " s4
� �
� �' � �
� ��rw c s$ e Zd ZdZd d
� fdd�
Z� ZS ) �_BuildMetaLegacyBackendaO 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.
r~ rS r] r r c
s� t tj�}tj�tj�|��}|tjvrtj�d|� tjd }|tjd< zt� j |d� W |tjd d �< |tjd< d S |tjd d �< |tjd< w )Nr rR )
r( ry r8 r7 �dirnamer� �insertrz �superr{ )r rS Zsys_pathZ
script_dirZ
sys_argv_0�� __class__r! r" r{ � s
� z!_BuildMetaLegacyBackend.run_setupr� r� )r$ r% r& rv r{ �
__classcell__r! r! r� r" r� � s r� c @ s e Zd ZdZdZdZdZdS )r� zAwheel.bdist_wheel is deprecated, please import it from setuptoolsz|
Ensure that any custom bdist_wheel implementation is a subclass of
setuptools.command.bdist_wheel.bdist_wheel.
)i� �
� z&https://github.com/pypa/wheel/pull/631N)r$ r% r& Z_SUMMARYZ_DETAILSZ _DUE_DATEZ_SEE_URLr! r! r! r" r� s
r� )rA r rB rC )Arv �
__future__r r1 rN r7 rb r� ry r� rP rV �collections.abcr r r �pathlibr �typingr r r r5 � r �_pathr r
Z_reqsr r r+ Zdistutils.utilr Ztyping_extensionsr �__all__�
BaseExceptionr �distr' r2 r6 r@ rL rT rY r] r( rZ �__annotations__r[ rw r� r� Z_BACKENDr r r r r r r r r r! r! r! r" �<module> sd
* J(