o

0i�?�@s�dZd
dl
Z
d
dlZd
dlZd
dlZd
dlZd
dlZd
dlZd
dlm	Z	
d
dl
mZ
d
dlm
Z

d
dlmZ
d
dlmZmZmZmZmZmZmZmZmZmZmZmZ
d
dlmZ
d
d	lmZ
d
d
l m!Z!
ddl"m#Z$
er~d
d
l%m&Z&
d
dl'm(Z(
d
dl)m*Z*
ej+Z,ee-ej.fZ/ed�
Z0eddd�Z1Gdd�d�Z2	dQdee-dee/dee-fdd�Z3dQdee-e4ee/fde-fdd�Z5dee/dee/fdd�Z6d ee4e/fde-fd!d"�Z7d e/de-fd#d$�Z8		dRd%e-d&eee-e-fdee/fd'd(�Z9d)e-d*ee/de
fd+d,�Z:d-e
d)e-defd.d/�Z;d)e-d&eee-e-fde/dee/ee-e-ffd0d1�Z<		dRd2e-d&eee-e-fdee/defd3d4�Z=		dRd5ee-e-fd&eee-e-fdee/dee-effd6d7�Z>dddd8�d9eee-e-fdee/dee-fd:d;�Z?d<e/d=e/de-fd>d?�Z@d@eeeee-eAfe-fde-fdAdB�ZBdCeCdeCfdDdE�ZD	dQdFeeEeCfdee/deee-ee-ffdGdH�ZFdSdJe-dee-eCffdKdL�ZGGdMdN�dN�ZHGdOdP�dPee0e1f�ZIdS)TaiUtility functions to expand configuration directives or special values
(such glob patterns).

We can split the process of interpreting configuration files into 2 steps:

1. The parsing the file contents from strings to value objects
   that can be understand by Python (for example a string with a comma
   separated list of keywords into an actual Python list of strings).

2. The expansion (or post-processing) of these values according to the
   semantics ``setuptools`` assign to them (for example a configuration field
   with the ``file:`` directive should be expanded from a list of file paths to
   a single string with the contents of those files concatenated)

This module focus on the second step, and therefore allow sharing the expansion
functions among several configuration file formats.

**PRIVATE MODULE**: API reserved for setuptools internal usage only.
�N)
�iglob)
�ConfigParser)
�
ModuleSpec)
�chain)�
TYPE_CHECKING�Callable�Dict�Iterable�Iterator�List�Mapping�Optional�Tuple�TypeVar�Union�cast)
�Path)
�
ModuleType)
�DistutilsOptionError�)
�	same_path)
�Distribution)
�ConfigDiscovery)
�DistributionMetadata�_K�_VT)
�	covariantc@sHeZ
dZd
Zdedefdd�Zdeee	j
e	j
ffdd�Zd	d
�ZdS)�StaticModulez>Proxy to a module object that avoids executing arbitrary code.�name�speccCs.t�
t�|j�
���
}t|�
�t��

|`	dS�
N)
�ast�parse�pathlibr�origin�
read_bytes�vars�update�locals�self)r)rr�module�r+�F/opt/osm/venv/lib/python3.10/site-packages/setuptools/config/expand.py�__init__Bs


zStaticModule.__init__�returnc

#s\�|jj
D]&�t�tj�r�f
d
d��jD�
EdH
qt�tj�r+�jr+�j�jfV
qdS)Nc
3s�|]}
|
�jfV
qdSr �
�value)�.0�target�
Z	statementr+r,�	<genexpr>Js�z1StaticModule._find_assignments.<locals>.<genexpr>)	r*�body�
isinstancer!�Assign�targets�	AnnAssignr0r2�
r)r+r3r,�_find_assignmentsGs�




��zStaticModule._find_assignmentsc
sLzt�f
d
d�|�
�D�
�
WSty%
}
zt|j�d����
|�d}~w
w)zHAttempt to load an attribute "statically", via :func:`ast.literal_eval`.c
3s4�|]\}
}t|
t
j�r|
j�krt
�|�
V
qdSr )r6r!�Name�id�literal_eval)r1r2r0�
�attrr+r,r4Qs�

�
��z+StaticModule.__getattr__.<locals>.<genexpr>z has no attribute N)�nextr;�	Exception�AttributeErrorr)r)r@�
er+r?r,�__getattr__Ns

�
��zStaticModule.__getattr__N)
�__name__�
__module__�__qualname__�__doc__�strrr-r
rr!�ASTr;rEr+r+r+r,r?s

r�patterns�root_dirr.c	s�hd
�
}g}�pt�
��|D]<�
t�
f
dd�|D�
�
r9tj�tj���
��
}|�t�f
dd�t|dd�D�
�
�

qtj�	�
���
tjd�}|�|�

q|S)a
Expand the list of glob patterns, but preserving relative paths.

    :param list[str] patterns: List of glob patterns
    :param str root_dir: Path to which globs should be relative
                         (current directory by default)
    :rtype: list
    >�
]�
{�
?�
}�
*�
[c
3s�|]}
|
�vV
qdSr r+)r1�charr/r+r,r4js�z glob_relative.<locals>.<genexpr>c
3s(�|]}
tj
�|
���tjd�V
qd
S)�
/N)�os�path�relpath�replace�sep�r1rW�
rMr+r,r4ms
��
�T)
�	recursiverU)
rV�getcwd�anyrW�abspath�join�extend�sortedrrXrYrZ�append)rLrMZglob_charactersZexpanded_valuesZ	glob_pathrWr+)rMr0r,�
glob_relativeZs





�
re�	filepathscsRd
dlm
}
tj��pt���
��f
dd�||�
D�
}d��f
dd�t|�
D�
�
S)z�Return the content of the files concatenated using ``
`` as str

    This function is sandboxed and won't reach anything outside ``root_dir``

    (By default ``root_dir`` is the current directory).
    r
)
�always_iterablec
3s�|]
}
tj
��|
�V
qdSr )rVrWrar[r\r+r,r4�s�zread_files.<locals>.<genexpr>�

c
3s"�|]}
t|
��rt
|
�
V
qdSr )�
_assert_local�
_read_filer[r\r+r,r4�s�
�

�)� setuptools.extern.more_itertoolsrgrVrWr`r^ra�_filter_existing_files)rfrMrgZ
_filepathsr+r\r,�
read_filesys

�rmc
cs6�|D]}
tj
�|
�
r|
V
qt�d
|
�d��

qdS)NzFile z cannot be found)rVrW�isfile�warnings�warn)rfrWr+r+r,rl�s�


�rl�filepathc
Cs:tj
|d
d��}
|
��Wd�
S1sw



Y
dS)Nzutf-8)
�encoding)�io�open�read)rq�
fr+r+r,rj�s

$�rjcCs@tt
j�|
�
�
tt
j�|�
�
jv
rd
|�d|
�d�}t|�
�
dS)NzCannot access z (or anything outside �
)T)rrVrWr`�parentsr)rqrM�msgr+r+r,ri�s"


ri�	attr_desc�package_dirc
Cs�|pt�
�}|���d
�
}|��}d
�|�
}|pd}t||
|�\}}}t||�}z	tt	||�|�WSt
yD


t||�}	t|	|�YSw)a�Reads the value of an attribute from a module.

    This function will try to read the attributed statically first
    (via :func:`ast.literal_eval`), and only evaluate the module if it fails.

    Examples:
        read_attr("package.attr")
        read_attr("package.module.attr")

    :param str attr_desc: Dot-separated string describing how to reach the
        attribute (see examples above)
    :param dict[str, str] package_dir: Mapping of package names to their
        location in disk (represented by paths relative to ``root_dir``).
    :param str root_dir: Path to directory containing all the packages in
        ``package_dir`` (current directory by default).
    :rtype: str
    �
.r-)rVr^�strip�split�popra�_find_module�
_find_spec�getattrrrB�
_load_spec)
rzr{rMZ
attrs_pathZ	attr_name�module_name�_parent_pathrWrr*r+r+r,�	read_attr�s











�r�r��module_pathcCs2tj
�||
�}|ptj
�|�
}|durt|�
�
|Sr )�	importlib�util�spec_from_file_location�	find_spec�ModuleNotFoundError)r�r�rr+r+r,r��s



r�rcCsFt|d
|
�}|t
jvrt
j|Stj�|�
}|t
j|<|j�|�

|S)NrF)r��sys�modulesr�r��module_from_spec�loader�exec_module)rr�rr*r+r+r,r��s









r�cCs�|}|�d
�
}|
rK|d|
vr>|
|d}|�
dd�}t|�
dkr/tj�||d�}|d}n|}d
�|g
|dd��
�
}n
d|
vrKtj�||
d�}tjj|g
|�d
�
�
R�}t|�d�tj�|d�ft|�d	��
�}	td
d�|	D�
d�}
||
|fS)a0
Given a module (that could normally be imported by ``module_name``
    after the build is complete), find the path to the parent directory where
    it is contained and the canonical name that could be used to import it
    considering the ``package_dir`` in the build configuration and ``root_dir``
    r|r
rU�
N�z.pyz__init__.pyz.*c
ss �|]}
tj
�|
�
r|
V
qdSr )rVrWrn�r1�
xr+r+r,r4���z_find_module.<locals>.<genexpr>)	r~�rsplit�lenrVrWrarrrA)r�r{rM�parent_path�module_partsZcustom_path�parts�
parent_moduleZ
path_start�
candidatesr�r+r+r,r��s(













�

r��qualified_class_namec
Cs^|pt�
�}|�d
�
}||dd�}|d|�}t||
|�\}}}tt||�|�}	t|	|�S)z@Given a qualified class name, return the associated class objectr|r�N)rVr^�rfindr�r�r�r�)
r�r{rM�idx�
class_name�pkg_namer�rWr�r*r+r+r,�
resolve_class�s






r��valuescs��
fd
d�|��D�
S)z�Given a dictionary mapping command names to strings for qualified class
    names, apply :func:`resolve_class` to the dict values.
    c
si|]\}
}|
t|��
��qSr+)
r��r1�
k�
v�r{rMr+r,�
<dictcomp>
�zcmdclass.<locals>.<dictcomp>)
�items)r�r{rMr+r�r,�cmdclass
sr�)�
namespaces�fill_package_dirrMr�c
s
d
dlm
}
d
dlm}m}
|rd
dlm}
nd
dlm}
|p!tj}|�	ddg
�}g}	|
dur1in
|
}
t
|||�
�
�
�t��
d	krVt�f
d
d�d|fD�
�
rV|
�
d�d
�
�D]-}
t||
�}|j|f
i|�
�
}|	�|�

|r�|
�d�
|
ks�tj�||�s�|
�|||
��

qX|	S)
aWorks similarly to :func:`setuptools.find_packages`, but with all
    arguments given as keyword arguments. Moreover, ``where`` can be given
    as a list (the results will be simply concatenated).

    When the additional keyword argument ``namespaces`` is ``True``, it will
    behave like :func:`setuptools.find_namespace_packages`` (i.e. include
    implicit namespaces as per :pep:`420`).

    The ``where`` argument will be considered relative to ``root_dir`` (or the current
    working directory when ``root_dir`` is not given).

    If the ``fill_package_dir`` argument is passed, this function will consider it as a
    similar data structure to the ``package_dir`` configuration parameter add fill-in
    any missing package location.

    :rtype: list
    r
)
�construct_package_dir)�unique_everseenrg)
�PEP420PackageFinder)
�
PackageFinder�wherer|Nr�c
3s �|]}
t�d|
�V
qd
S)r
N)
�
_same_pathr��
�searchr+r,r4=
r�z find_packages.<locals>.<genexpr>r�)�setuptools.discoveryr�rkr�rgr�r�rV�curdirr�listr��all�
setdefault�
_nest_path�findrb�getrW�samefiler')
r�r�rM�kwargsr�r�rgr�r��packagesrW�package_pathZpkgsr+r�r,�
find_packages
s.






&








��r��parentrWcCs&|
d
vr|ntj
�||
�}
tj
�|
�
S)N>r�r|)rVrWra�normpath)r�rWr+r+r,r�M
s

r�r0c

CsXt|�
r|�}t
ttttf|�}t|t�s*t|d
�r&d�t	t|��
}|Sd|}|S)z`When getting the version directly from an attribute,
    it should be normalised to string.
    �__iter__r|z%s)
�callablerr	rrJ�intr6�hasattrra�mapr/r+r+r,�versionR
s




�r��package_datac

Csd
|vr|�d
�
|d<|S)NrRr�)
r)
r�r+r+r,�canonic_package_datad
s


r��
data_filescs$t|t
�r|S�f
d
d�|��D�
S)z�For compatibility with ``setup.py``, ``data_files`` should be a list
    of pairs instead of a dict.

    This function also expands glob patterns.
    c
sg|]\}
}|
t|��f�qSr+)
re)r1�destrLr\r+r,�
<listcomp>u
s��z&canonic_data_files.<locals>.<listcomp>)r6r�r�)r�rMr+r\r,�canonic_data_filesj
s



�r��entry-points�textcCsBtd
dd�}t
|_|�||
�
dd�|��D�
}|�|jd
�
|S)a?
Given the contents of entry-points file,
    process it into a 2-level dictionary (``dict[str, dict[str, str]]``).
    The first level keys are entry-point groups, the second level keys are
    entry-point names, and the second level values are references to objects
    (that correspond to the entry-point value).
    N)
�
=)�default_section�
delimitersc
Ssi|]\}
}|
t|�
��
�qSr+)�dictr�r�r+r+r,r��
r�z entry_points.<locals>.<dictcomp>)rrJ�optionxform�read_stringr�rr�)r�Ztext_source�parser�groupsr+r+r,�entry_points{
s




r�c@sbeZ
dZd
Zddd�Zdd�Zdd	�Zd
d�Zdee	e	ffd
d�Z
edee	e	ffdd��
ZdS)�EnsurePackagesDiscovereda�
Some expand functions require all the packages to already be discovered before
    they run, e.g. :func:`read_attr`, :func:`resolve_class`, :func:`cmdclass`.

    Therefore in some cases we will need to run autodiscovery during the evaluation of
    the configuration. However, it is better to postpone calling package discovery as
    much as possible, because some parameters can influence it (e.g. ``package_dir``),
    and those might not have been processed yet.
    �distributionrcCs|
|_d
|_
dS)NF)�_dist�_called)r)r�r+r+r,r-�
�


z!EnsurePackagesDiscovered.__init__c

Cs"|jsd
|_|j
jdd�

dSdS)zBTrigger the automatic package discovery, if it is still necessary.TF)
rN)r�r��set_defaultsr:r+r+r,�__call__�
s

�z!EnsurePackagesDiscovered.__call__c


Cs|Sr r+r:r+r+r,�	__enter__�
s
z"EnsurePackagesDiscovered.__enter__cCs|jr|j
j��
dSdSr )r�r�r�Zanalyse_name)r)Z	_exc_typeZ
_exc_valueZ
_tracebackr+r+r,�__exit__�
s

�z!EnsurePackagesDiscovered.__exit__r.c
Cs|�
|jj
}
|
dur
iS|
Sr )r�r{)r)Zpkg_dirr+r+r,�_get_package_dir�
s


z)EnsurePackagesDiscovered._get_package_dirc

Cs
t|j
�
S)
zCProxy to ``package_dir`` that may trigger auto-discovery when used.)�LazyMappingProxyr�r:r+r+r,r{�
s
z$EnsurePackagesDiscovered.package_dirN)r�r)
rFrGrHrIr-r�r�r�rrJr��propertyr{r+r+r+r,r��
s

	
r�c@sveZ
dZd
Zdegeeefffdd�Zdeeeffdd�Z	dedefd	d
�Z
defdd�Zde
efd
d�ZdS)r�a�
Mapping proxy that delays resolving the target object, until really needed.

    >>> def obtain_mapping():
    ...     print("Running expensive function!")
    ...     return {"key": "value", "other key": "other value"}
    >>> mapping = LazyMappingProxy(obtain_mapping)
    >>> mapping["key"]
    Running expensive function!
    'value'
    >>> mapping["other key"]
    'other value'
    �obtain_mapping_valuecCs|
|_d|_
dSr )�_obtain�_value)r)r�r+r+r,r-�
r�zLazyMappingProxy.__init__r.c

Cs|jdur
|�
�|_|jSr )r�r�r:r+r+r,�_target�
s




zLazyMappingProxy._target�keycCs|��|
Sr )
r�)r)r�r+r+r,�__getitem__�
�
zLazyMappingProxy.__getitem__c

C�t|�
��
Sr )r�r�r:r+r+r,�__len__�
r�zLazyMappingProxy.__len__c

Cr�r )�iterr�r:r+r+r,r��
r�zLazyMappingProxy.__iter__N)rFrGrHrIrrrrr-r�r�r�r�r
r�r+r+r+r,r��
s

r�r )NN)
r�)JrIr!r�rsrVr#r�ro�globr�configparserr�importlib.machineryr�	itertoolsr�typingrrrr	r
rrr
rrrrr�typesrZdistutils.errorsr�_pathrr�Zsetuptools.distrr�r�distutils.distr�
from_iterableZ
chain_iterrJ�PathLikeZ_Pathrrrre�bytesrmrlrjrir�r�r�r�r�r�r�r�r�r�r�r�r�r�r�r�r�r+r+r+r,�<module>
s�









8







�
�
�
�"

�
��
�&


�
�
�
�$
�
���
�
�

���

�


���
�6(�

�
�
�&