Файловый менеджер - Редактировать - /home/digitalm/venv/lib/python3.7/site-packages/setuptools/command/__pycache__/build_py.cpython-37.pyc
Назад
B �5�g�: � @ s� d dl mZ d dlmZ d dlmZ d dlm mZ d dl Z d dl Z d dl Z d dl Z d dl Zd dlZd dlZd dlmZ d dlmZmZmZmZmZmZ ddlmZ dd l m Z d d � Z G d d � d ej�Zdd� Z G dd� d�Z dS )� )�partial)�glob)� convert_pathN)�Path)�Dict�Iterable�Iterator�List�Optional�Tuple� )�unique_everseen)� SetuptoolsDeprecationWarningc C s t �| t �| �jtjB � d S )N)�os�chmod�stat�st_mode�S_IWRITE)�target� r �C/tmp/pip-install-251nq386/setuptools/setuptools/command/build_py.py� make_writable s r c s@ e Zd ZU dZdZeed< dZee ed< dd� Z d5� fd d � Z d d � Z d d� Z dd� Zdd� Zdd� Zdd� Zdd� Zd6ee d�� fdd� Zee e f d�d d �Zeee e f d�d d �Zeee e f d�d d!�Zd"d#� Zd$d%� Z e e e ee d&�d'd(�Z d)d*� Z d+d,� Z d-d.� Z!d/d0� Z"d1d2� Z#e$d3d4� �Z%� Z&S )7�build_pyaX Enhanced 'build_py' command that includes data files with packages The data files are specified via a 'package_data' argument to 'setup()'. See 'setuptools.dist.Distribution' for more details. Also, this version of the 'build_py' command allows you to specify both 'py_modules' and 'packages' in the same setup operation. F� editable_modeN�existing_egg_info_dirc C s@ t j�| � | jj| _| jjp i | _d| jkr6| jd= g | _d S )N� data_files)�origr �finalize_options� distribution� package_data�exclude_package_data�__dict__�_build_py__updated_files)�selfr r r r # s zbuild_py.finalize_options� c s: |r$t t|��� �}t t|��� �}t� �||||||�S )N)�strr �resolve�super� copy_file)r# �infile�outfile� preserve_mode�preserve_times�link�level)� __class__r r r( + s zbuild_py.copy_filec C sT | j s | jr| jrdS | j r$| �� | jr:| �� | �� | �tjj | dd�� dS )z?Build modules, packages, and copy data files to build directoryNr )�include_bytecode) � py_modules�packagesr Z build_modulesZbuild_packages�build_package_data� byte_compiler r � get_outputs)r# r r r �run4 s z build_py.runc C s& |dkr| � � | _| jS tj�| |�S )zlazily compute data filesr )�_get_data_filesr r r � __getattr__)r# �attrr r r r8 D s zbuild_py.__getattr__c C s. t j�| |||�\}}|r&| j�|� ||fS )N)r r � build_moduler" �append)r# �module� module_file�packager* �copiedr r r r: K s zbuild_py.build_modulec C s | � � tt| j| jpd��S )z?Generate list of '(package,src_dir,build_dir,filenames)' tuplesr )�analyze_manifest�list�map�_get_pkg_data_filesr2 )r# r r r r7 Q s zbuild_py._get_data_filesc C s$ | j �di � tt| j| jp d��S )z� Generate list of ``(package,src_dir,build_dir,filenames)`` tuples, but without triggering any attempt to analyze or build the manifest. �manifest_filesr )r! � setdefaultrA rB rC r2 )r# r r r � get_data_files_without_manifestV s z(build_py.get_data_files_without_manifestc sJ | � |�� tjj| jg|�d� � }� fdd�| �|� �D �}|� ||fS )N�.c s g | ]}t j�|� ��qS r )r �path�relpath)�.0�file)�src_dirr r � <listcomp>i s z0build_py._get_pkg_data_files.<locals>.<listcomp>)�get_package_dirr rH �join� build_lib�split�find_data_files)r# r> � build_dir� filenamesr )rL r rC ` s z build_py._get_pkg_data_filesc C s` | � | j||�}tttdd�|�}tj�|�}tt j j |�}t�| j � |g �|�}| �|||�S )z6Return filenames for package's data files in 'src_dir'T)� recursive)�_get_platform_patternsr rB r r � itertools�chain� from_iterable�filterr rH �isfilerD �get�exclude_data_files)r# r> rL �patternsZglobs_expandedZ globs_matchesZ glob_files�filesr r r rR n s zbuild_py.find_data_files)�returnc s" | j rt| �� �� �S t� �|�S )z1See :class:`setuptools.commands.build.SubCommand`)r rA �get_output_mapping�keysr' r5 )r# r0 )r/ r r r5 s zbuild_py.get_outputsc C s( t �| �� | �� �}tt|dd� d��S )z1See :class:`setuptools.commands.build.SubCommand`c S s | d S )Nr r )�xr r r �<lambda>� � z-build_py.get_output_mapping.<locals>.<lambda>)�key)rW rX � _get_package_data_output_mapping�_get_module_mapping�dict�sorted)r# �mappingr r r ra � s zbuild_py.get_output_mappingc c s@ x:| � � D ].\}}}|�d�}| �| j||�}||fV q W dS )z5Iterate over all modules producing (dest, src) pairs.rG N)Zfind_all_modulesrQ Zget_module_outfilerP )r# r> r< r= �filenamer r r rh � s z build_py._get_module_mappingc c sP xJ| j D ]@\}}}}x2|D ]*}tj�||�}tj�||�}||fV qW qW dS )z6Iterate over package data producing (dest, src) pairs.N)r r rH rO )r# r> rL rS rT rl r �srcfiler r r rg � s z)build_py._get_package_data_output_mappingc C sD x>| � � D ]2\}}| �tj�|�� | �||�\}}t|� q W dS )z$Copy data files into build directoryN)rg �mkpathr rH �dirnamer( r )r# r rm Z_outfZ_copiedr r r r3 � s zbuild_py.build_package_datac C sv i | _ }| jjsd S i }x$| jp$dD ]}||t| �|��< q&W t| dd �r~t| jd�� � r~| j}t|d�}|j dd�� � }n"| � d� | � d�}|j}|jj}t� }x�| �||�D ]�} tj�t| ��\} } d } | } x@| �r| | k�r| |k�r| } tj�| �\} }tj�|| �} q�W | |kr�| | k�r8|�| ��rXq�n |�|| | �}|�rX|�|� |�|| g ��| � q�W d S )Nr r z SOURCES.txtzutf-8)�encoding�egg_info) rD r Zinclude_package_datar2 �assert_relativerN �getattrr r �existsZ read_text� splitlines� run_command�get_finalized_commandrq �filelistr_ �_IncludePackageDataAbuse�_filter_build_filesr rH rQ rO � is_module�importable_subpackage�warnrE r; )r# ZmfZsrc_dirsr> � egg_info_dir�manifestr_ Zei_cmd�checkrH �d�f�prevZoldfZdf� importabler r r r@ � s@ zbuild_py.analyze_manifest)r_ rq r` c # sp | � d�}|| j|j|jf}dd� |D �}x@|D ]8}tj�|�� tj�|�rbt� fdd�|D ��r0|V q0W dS )a} ``build_meta`` may try to create egg_info outside of the project directory, and this can be problematic for certain plugins (reported in issue #3500). Extensions might also include between their sources files created on the ``build_lib`` and ``build_temp`` directories. This function should filter this case of invalid files out. �buildc S s g | ]}|rt j�|��qS r )r rH �normpath)rJ �pr r r rM � s z0build_py._filter_build_files.<locals>.<listcomp>c 3 s | ]}|� kV qd S )Nr )rJ r� )� norm_pathr r � <genexpr>� s z/build_py._filter_build_files.<locals>.<genexpr>N) rw rP � build_temp� build_baser rH r� �isabs�all)r# r_ rq r� Z build_dirsZ norm_dirsrK r )r� r rz � s "z build_py._filter_build_filesc C s d S )Nr )r# r r r �get_data_files� s zbuild_py.get_data_filesc C s� y | j | S tk r Y nX tj�| ||�}|| j |< |rF| jjsJ|S x,| jjD ] }||ksn|�|d �rTP qTW |S t� |d��}|� � }W dQ R X d|kr�t j � d|f ��|S )z8Check namespace packages' __init__ for declare_namespacerG �rbNs declare_namespacez�Namespace package problem: %s is a namespace package, but its __init__.py does not call declare_namespace()! Please fix it. (See the setuptools manual under "Namespace Packages" for details.) ")�packages_checked�KeyErrorr r � check_packager Znamespace_packages� startswith�io�open�read� distutils�errors�DistutilsError)r# r> � package_dirZinit_py�pkgr� �contentsr r r r� � s& zbuild_py.check_packagec C s" i | _ tj�| � d| _d | _d S )NF)r� r r �initialize_optionsr r )r# r r r r� s zbuild_py.initialize_optionsc C s0 t j�| |�}| jjd k r,tj�| jj|�S |S )N)r r rN r Zsrc_rootr rH rO )r# r> �resr r r rN s zbuild_py.get_package_dirc s\ t ���| �| j||�}�fdd�|D �}tj�|�}t|�� � fdd��D �}t t|��S )z6Filter filenames for package's data files in 'src_dir'c 3 s | ]}t �� |�V qd S )N)�fnmatchrZ )rJ �pattern)r_ r r r� s z.build_py.exclude_data_files.<locals>.<genexpr>c 3 s | ]}|� kr|V qd S )Nr )rJ �fn)�badr r r� s )rA rV r rW rX rY �setr )r# r> rL r_ r^ Z match_groups�matchesZkeepersr )r� r_ r r] s zbuild_py.exclude_data_filesc s. t �| �dg �| �|g ��}� fdd�|D �S )z� yield platform-specific path patterns (suitable for glob or fn_match) from a glob-based spec (such as self.package_data or self.exclude_package_data) matching package in src_dir. � c 3 s | ]}t j�� t|��V qd S )N)r rH rO r )rJ r� )rL r r r� * s z2build_py._get_platform_patterns.<locals>.<genexpr>)rW rX r\ )�specr> rL Z raw_patternsr )rL r rV s z build_py._get_platform_patterns)r$ r$ Nr$ )r$ )'�__name__� __module__� __qualname__�__doc__r �bool�__annotations__r r r% r r( r6 r8 r: r7 rF rC rR r r5 r ra r r rh rg r3 r@ r rz r� r� r� rN r] � staticmethodrV � __classcell__r r )r/ r r s4 ) r c C s: t j�| �s| S ddlm} t�d��� | }||��d S )Nr )�DistutilsSetupErrorz� Error: setup script specifies an absolute path: %s setup() arguments must *always* be /-separated paths relative to the setup.py directory, *never* absolute paths. )r rH r� �distutils.errorsr� �textwrap�dedent�lstrip)rH r� �msgr r r rr / s rr c @ s@ e Zd ZdZG dd� de�Zdd� Zdd� Zdd � Zd d � Z d S ) ry z>Inform users that package or module is included as 'data file'c @ s e Zd ZdZdZdS )z!_IncludePackageDataAbuse._WarningzU Package {importable!r} is absent from the `packages` configuration. a| ############################ # Package would be ignored # ############################ Python recognizes {importable!r} as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that {importable!r} is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want {importable!r} to be distributed and are already explicitly excluding {importable!r} via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. N)r� r� r� Z_SUMMARYZ_DETAILSr r r r �_WarningG s $r� c C s t � | _d S )N)r� �_already_warned)r# r r r �__init__r s z!_IncludePackageDataAbuse.__init__c C s |� d�o |d td� � �� S )Nz.py)�endswith�len� isidentifier)r# rK r r r r{ u s z"_IncludePackageDataAbuse.is_modulec C s6 t |�j}tt�tj|j��}|r2d�|f|��S d S )NrG ) r �parentrA rW � takewhiler% r� �partsrO )r# r� rK r� r� r r r r| x s z._IncludePackageDataAbuse.importable_subpackagec C s( || j kr$| jj|d� | j �|� d S )N)r� )r� r� �emit�add)r# r� r r r r} s z _IncludePackageDataAbuse.warnN) r� r� r� r� r r� r� r{ r| r} r r r r ry D s +ry )!� functoolsr r �distutils.utilr Zdistutils.command.build_py�commandr r r r� r� r� r� r� rW r Zpathlibr �typingr r r r r r Zextern.more_itertoolsr �warningsr r rr ry r r r r �<module> s(
| ver. 1.4 |
Github
|
.
| PHP 8.3.23 | Генерация страницы: 0.05 |
proxy
|
phpinfo
|
Настройка