📁 File Manager Pro
v10.0.2 | PHP: 8.1.34
Server: LiteSpeed
2026-06-27 07:36:17
📂
/
/
opt
/
alt
/
python38
/
lib
/
python3.8
/
site-packages
/
setuptools
/
__pycache__
✏️
Editing: build_meta.cpython-38.pyc
U �Re(( � @ s d Z ddlZddlZddlZddlZddlZddlZddlZddlZddl Z ddl m Z dddddd d gZ G d d � d e �ZG d d � d ejj�Zejdd� �Zdd� Zdd� Zdd� ZG dd� de�ZG dd� de�Ze� ZejZejZej Z ej Z ej Z e� 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)�parse_requirements� get_requires_for_build_sdist� get_requires_for_build_wheel� prepare_metadata_for_build_wheel� build_wheel� build_sdist� __legacy__�SetupRequirementsErrorc @ s e Zd Zdd� ZdS )r c C s || _ d S �N)� specifiers)�selfr � r ��/builddir/build/BUILDROOT/alt-python38-setuptools-58.3.0-2.el8.x86_64/opt/alt/python38/lib/python3.8/site-packages/setuptools/build_meta.py�__init__4 s z SetupRequirementsError.__init__N)�__name__� __module__� __qualname__r r r r r r 3 s c @ s& e Zd Zdd� Zeejdd� ��ZdS )� Distributionc C s t ttt|���}t|��d S r )�list�map�strr r )r r Zspecifier_listr r r �fetch_build_eggs9 s z Distribution.fetch_build_eggsc c s* t jj}| t j_z dV W 5 |t j_X dS )zw Replace distutils.dist.Distribution with this class for the duration of this context. N)� distutils�corer )�cls�origr r r �patch> s zDistribution.patchN)r r r r � classmethod� contextlib�contextmanagerr r r r r r 8 s r c c s( t j} dd� t _z dV W 5 | t _X dS )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>W � z+no_install_setup_requires.<locals>.<lambda>N)� setuptoolsZ_install_setup_requires)r r r r �no_install_setup_requiresN s r$ 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 �z1_get_immediate_subdirectories.<locals>.<listcomp>)r% �listdirr+ r r+ r � _get_immediate_subdirectories^ s r. c sD � fdd�t �| �D �}z |\}W n tk r> td��Y nX |S )Nc 3 s | ]}|� � �r|V qd S r ��endswith�r) �f�� extensionr r � <genexpr>d s �z'_file_with_extension.<locals>.<genexpr>z[No distribution was found. Ensure that `setup.py` is not empty and that it calls `setup()`.)r% r- � ValueError)� directoryr4 Zmatching�filer r3 r �_file_with_extensionc s � � r9 c C s& t j�| �st�d�S ttdt�| �S )Nz%from setuptools import setup; setup()�open)r% r& �exists�io�StringIO�getattr�tokenizer: �� setup_scriptr r r �_open_setup_scriptq s rB c @ s` e Zd Zdd� Zdd� Zddd�Zdd d �Zdd d �Zdd d�Zdd� Z ddd�Z ddd�Z dS )�_BuildMetaBackendc C s |pi }|� dg � |S )N�--global-option)� setdefault�r �config_settingsr r r � _fix_config{ s z _BuildMetaBackend._fix_configc C sz | � |�}tjd d� dg |d t_z t�� � | �� W 5 Q R X W n, tk rt } z||j7 }W 5 d }~X Y nX |S )N� �egg_inforD )rH �sys�argvr r � run_setupr r )r rG � requirements�er r r �_get_build_requires� s � z%_BuildMetaBackend._get_build_requires�setup.pyc C sD |}d}t |��}|�� �dd�}W 5 Q R X tt||d�t� � d S )N�__main__z\r\nz\n�exec)rB �read�replacerS �compile�locals)r rA �__file__r r2 �coder r r rM � s z_BuildMetaBackend.run_setupNc C s | � |�}| j|dgd�S )N�wheel�rN �rH rP rF r r r r � s �z._BuildMetaBackend.get_requires_for_build_wheelc C s | � |�}| j|g d�S )Nr[ r\ rF r r r r � s z._BuildMetaBackend.get_requires_for_build_sdistc C s� t jd d� dd|g t _t� � | �� W 5 Q R X |}dd� t�|�D �}t|�dkr�tt|��dkr�tj� |t�|�d �}q8t|�dks�t �q�q8||kr�t � tj� ||d �|� t j |dd� |d S ) NrI Z dist_infoz --egg-basec S s g | ]}|� d �r|�qS )z .dist-infor/ r1 r r r r, � s �zF_BuildMetaBackend.prepare_metadata_for_build_wheel.<locals>.<listcomp>r T)� ignore_errors)rK rL r$ rM r% r- �lenr. r& r( �AssertionError�shutil�move�rmtree)r �metadata_directoryrG Zdist_info_directoryZ dist_infosr r r r � s6 � �� ��z2_BuildMetaBackend.prepare_metadata_for_build_wheelc C s� | � |�}tj�|�}tj|dd� tj|d���}tjd d� | d|g |d t_t � � | � � W 5 Q R X t ||�}tj� ||�}tj� |�r�t�|� t�tj� ||�|� W 5 Q R X |S )NT)�exist_ok)�dirrI z --dist-dirrD )rH r% r& �abspath�makedirs�tempfile�TemporaryDirectoryrK rL r$ rM r9 r( r; �remove�rename)r Z setup_commandZresult_extensionZresult_directoryrG Z tmp_dist_dirZresult_basename� result_pathr r r �_build_with_temp_dir� s( �� � z&_BuildMetaBackend._build_with_temp_dirc C s | � dgd||�S )N� bdist_wheelz.whl�rm )r �wheel_directoryrG rc r r r r � s �z _BuildMetaBackend.build_wheelc C s | � dddgd||�S )N�sdistz --formats�gztarz.tar.gzro )r �sdist_directoryrG r r r r � s �z _BuildMetaBackend.build_sdist)rQ )N)N)N)NN)N) r r r rH rP rM r r r rm r r r r r r rC y s � " � rC 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. rQ c s� t tj�}tj�tj�|��}|tjkr6tj�d|� tjd }|tjd< ztt | �j |d� W 5 |tjd d �< |tjd< X d S )Nr r@ ) r rK r& r% �dirnamerf �insertrL �superrt rM )r rA �sys_pathZ script_dirZ sys_argv_0�� __class__r r rM � s �� z!_BuildMetaLegacyBackend.run_setup)rQ )r r r �__doc__rM � __classcell__r r ry r rt � s rt ) r{ r< r% rK r? r` r rh r# r � pkg_resourcesr �__all__� BaseExceptionr �distr r r$ r. r9 rB �objectrC rt Z_BACKENDr r r r r r r r r r �<module> sD � m)
💾 Save Changes
❌ Cancel