File: //opt/saltstack/salt/lib/python3.10/site-packages/setuptools/__pycache__/build_meta.cpython-310.pyc
o
�N�g{N � @ s� d Z ddlZddlZddlZddlZddlZddlZddlZddlZddl Z ddl
m Z ddl m
Z
mZmZmZmZ ddlZddlZddlmZ ddlmZ ddlmZ dd l mZ dd
lm Z g d �Z e� d d
�� � Z de �!dd�v Z"G dd� de#�Z$G dd� dej%j&�Z&ej'dd� �Z(dd� Z)dd� Z*dd � Z+ej'd d � �Z,ee
e-ee-ee- df f Z. G d d � d �Z/G d!d"� d"e/�Z0G d#d$� d$e0�Z1e0� Z2e2j3Z3e2j4Z4e2j5Z5e2j6Z6e2j7Z7e"s�e2j8Z8e2j9Z9e2j:Z:e1� 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
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 @ s e Zd Zdd� ZdS )r c C s
|| _ d S �N)�
specifiers)�selfr � r �I/opt/saltstack/salt/lib/python3.10/site-packages/setuptools/build_meta.py�__init__D �
z SetupRequirementsError.__init__N)�__name__�
__module__� __qualname__r! r r r r r C s r c @ s& e Zd Zdd� Zeejdd� ��ZdS )� Distributionc C s t t|��}t|��r )�listr r )r r Zspecifier_listr r r �fetch_build_eggsI s z Distribution.fetch_build_eggsc 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 �patchN s �zDistribution.patchN)r# r$ r% r( � classmethod�
contextlib�contextmanagerr- r r r r r& H 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 )Zattrsr r r �<lambda>g s z+no_install_setup_requires.<locals>.<lambda>N)�
setuptoolsZ_install_setup_requires)r, r r r �no_install_setup_requires^ s �
r3 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>o s
��z1_get_immediate_subdirectories.<locals>.<listcomp>)r4 �listdirr: r r: r � _get_immediate_subdirectoriesn s
�r= c s< � fdd�t �| �D �}z|\}W |S ty td��w )Nc 3 s � | ]
}|� � �r|V qd S r ��endswith�r8 �f�� extensionr r � <genexpr>u s � z'_file_with_extension.<locals>.<genexpr>z[No distribution was found. Ensure that `setup.py` is not empty and that it calls `setup()`.)r4 r< �
ValueError)� directoryrC Zmatching�filer rB r �_file_with_extensiont s ���rH c C s& t j�| �s t�d�S ttdt�| �S )Nz%from setuptools import setup; setup()�open)r4 r5 �exists�io�StringIO�getattr�tokenizerI �� setup_scriptr r r �_open_setup_script� s
rQ 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
�
"�rV c @ s� e Zd ZdZdededee fdd�Zdd� Zdede e fd d
�Z
dede e fd d �Z dede e fd
d�Z dede e fdd�Z
dS )�_ConfigSettingsTranslatorz�Translate ``config_settings`` into distutils-style command arguments.
Only a limited number of options is currently supported.
�key�config_settings�returnc 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�
isinstance�str�shlex�split)r rX rY �cfg�optsr r r � _get_config� s z%_ConfigSettingsTranslator._get_configc C s" dd� t jjjD �}dd� |D �S )z>Global options accepted by setuptools (e.g. quiet or verbose).c s s � | ] }|d d� V qd S )N� r )r8 �optr r r rD � s � zB_ConfigSettingsTranslator._valid_global_options.<locals>.<genexpr>c S s h | ] }|D ]}|r|�qqS r r )r8 Zlong_and_short�flagr r r � <setcomp>� s zB_ConfigSettingsTranslator._valid_global_options.<locals>.<setcomp>)r2 �distr& �global_options)r �optionsr r r �_valid_global_options� s z/_ConfigSettingsTranslator._valid_global_optionsc # 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 |�}� fd
d �|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']
> �no�false�0Zoff�verbosez --verbose�1z-qz-v�quietz--quiet�--global-optionc 3 s" � | ] }|� d �� v r|V qdS )r N)�strip)r8 �arg�Zvalidr r rD � s � z9_ConfigSettingsTranslator._global_args.<locals>.<genexpr>N)r] r[ �lowerrj rb )r rY r` Zfalsey�level�argsr rt 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-daterl z
--tag-datez --no-datez tag-buildz --tag-buildN)r
r] )r rY r` �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 rY r` �moder r r �_editable_args� s �
z(_ConfigSettingsTranslator._editable_argsc c sx � | � d|�}| �� }g }|D ]}|�d�|vr |�|� |V q| � d|�E dH |r:tjdd|�d�dd � dS 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']
>>> warnings.simplefilter('error', SetuptoolsDeprecationWarning)
>>> list(fn({'--global-option': 'foo'})) # doctest: +IGNORE_EXCEPTION_DETAIL
Traceback (most recent call last):
SetuptoolsDeprecationWarning: ...arguments given via `--global-option`...
rq r z--build-optionNz7Incompatible `config_settings` passed to build backend.z
The arguments z� were given via `--global-option`.
Please use `--build-option` instead,
`--global-option` is reserved for flags like `--verbose` or `--quiet`.
)i� � � )Zdue_date)rb rj rr �appendr �emit)r rY rw Z global_optsZbad_argsrs r r r �_arbitrary_args
s& �
��
��z)_ConfigSettingsTranslator._arbitrary_argsN)r# r$ r% �__doc__r] �_ConfigSettingsr rb rj r rx Z)_ConfigSettingsTranslator__dist_info_argsr{ r� r r r r rW � s "rW c @ s� e Zd Zdd� Zd"dd�Zd#dd�Zd#d d
�Zd ed ed
efdd�Zd ed ed
e fdd�Z
d#dd�Z dd� Z d$dd�Z
d#dd�Zd ee d
ee fdd�Zesd d$d d �Zd#d d �Z d#d d!�ZdS dS )%�_BuildMetaBackendc
C s� g t jd d� �| �|��d�| �|��t _z t�� � | �� W d � W |S 1 s,w Y W |S tyK } z ||j7 }W Y d }~|S d }~ww )Nr Zegg_info) �sys�argvrx r� r& r- � run_setupr r )r rY � requirements�er r r �_get_build_requires< s* ����
�����z%_BuildMetaBackend._get_build_requires�setup.pyc
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) r4 r5 �abspathrQ �read�replace�exec�locals�
SystemExit�coder r )r rP �__file__r# rA r� r� r r r r� K s"
����z_BuildMetaBackend.run_setupNc C s | j |dgd�S )NZwheel�r� �r� �r rY r r r r b s z._BuildMetaBackend.get_requires_for_build_wheelc C s | j |g d�S )Nr� r� r� r r r r e s z._BuildMetaBackend.get_requires_for_build_sdist�metadata_directory�suffixrZ c 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] r9 )r r� r� �info_dirr r r �_bubble_up_info_directoryh s z+_BuildMetaBackend._bubble_up_info_directoryc s� t �|�D ]1\}}}� fdd�|D �}t|�dks t|�dkr6t|�dks-J d� � d���t||d � S qd� � d|� �}t�|��) Nc s g | ] }|� � �r|�qS r r> r@ �r� r r r; w s z:_BuildMetaBackend._find_info_directory.<locals>.<listcomp>r r z Multiple z directories foundzNo z directory found in )r4 �walk�lenr r Z
InternalError)r r� r� r� �dirsr Z
candidates�msgr r� r r� u s �
z&_BuildMetaBackend._find_info_directoryc C st g t jd d� �| �|��d�d�|�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)r� r� rx r3 r� r� �r r� rY r r r r � s$ ������
� z2_BuildMetaBackend.prepare_metadata_for_build_wheelc C s t j�|�}t j|dd� d|d�}tjdi |���\}g tjd d� �| �|��|�d�|�| � |��t_t
� � | � � W d � n1 sGw Y t ||�}t j�
||�}t j�|�rct �|� t �t j�
||�|� W d � |S 1 syw Y |S )NT)�exist_okz.tmp-)�prefix�dirr z
--dist-dirr )r4 r5 r� �makedirs�tempfileZTemporaryDirectoryr� r� rx r� r3 r� rH r7 rJ �remove�rename) r Z
setup_commandZresult_extensionZresult_directoryrY Z temp_optsZ tmp_dist_dirZresult_basename� result_pathr r r �_build_with_temp_dir� s:
������
�
��z&_BuildMetaBackend._build_with_temp_dirc C s< t � � | �dgd||�W d � S 1 sw Y d S )NZ bdist_wheel�.whl)rV r� )r �wheel_directoryrY r� r r r r � s
�$�z _BuildMetaBackend.build_wheelc C s | � g d�d||�S )N)Zsdistz --formats�gztarz.tar.gz)r� )r Zsdist_directoryrY r r r r � s �z _BuildMetaBackend.build_sdistc 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 )Nz--dist-info-dirZeditable_wheelr� )r� r{ rV r� )r r� rY r� r� ra �cmdr r r r � s
�$�z _BuildMetaBackend.build_editablec C s
| � |�S r )r r� r r r r � r" 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� r )NN)r# r$ r% r� r� r r r] r� r r� r r� r r r r� �LEGACY_EDITABLEr r r r r r r r� ; s*
�
�
�
��r� c s" e Zd ZdZd� 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� c
s� t tj�}tj�tj�|��}|tjvrtj�d|� tjd }|tjd< ztt | �j
|d� W |tjd d �< |tjd< d S |tjd d �< |tjd< w )Nr rO ) r' r� r5 r4 �dirnamer� �insertr� �superr� r� )r rP Zsys_pathZ
script_dirZ
sys_argv_0�� __class__r r r� � s
� z!_BuildMetaLegacyBackend.run_setupr� )r# r$ r% r� r� �
__classcell__r r r� r r� � s r� )<r� rK r4 r^ r� rN r� r/ r� rS �pathlibr �typingr r r r r r2 r) r r �_pathr
Z_reqsr r Zdistutils.utilr
�__all__�getenvru r r� r� �
BaseExceptionr rg r& r0 r3 r= rH rQ rV r] r� rW r� r� Z_BACKENDr r r r r r r r r r r r r �<module> sb
$)