Файловый менеджер - Редактировать - /home/digitalm/venv/lib/python3.7/site-packages/setuptools/command/__pycache__/editable_wheel.cpython-37.pyc
Назад
B �5�g�| � @ sV d Z ddlZddlZddlZddlZddlZddlmZ ddlm Z ddl m Z ddl m Z ddlmZ ddlmZ dd lmZmZmZmZmZmZmZmZmZm Z d d l m Z m Z m Z m!Z!m"Z" d d l#m$Z$ d d l%m&Z& d dl'm(Z(m)Z)m*Z* ddl+m+Z, e�r ddl-m.Z. ej/dk�r$ddlm0Z0 n e�r8ddl1m0Z0 n ddl2m3Z0 e e4ef Z5ede5d�Z6e�7e8�Z9G dd� de �Z:dZ;dZ<G dd � d e �Z=G d d � d e0�Z>G d d � d �Z?G d!d"� d"e?�Z@G d#d$� d$�ZAeeBd%�d&d'�ZCee4 ee4e4f eeBd(�d)d*�ZDd+d,� ZEe&ee4 d-�d.d/�ZFe&ee4 d-�d0d1�ZGee4 ee4e4f e5ee4e4f d2�d3d4�ZHe5e4d5�d6d7�ZIee4e4f ee4 d8�d9d:�ZJee4 ee4e4f eee4ee4 f d;�d<d=�ZKee4e4f ee4e4f d8�d>d?�ZLe4e4e4e4eBd@�dAdB�ZMe6e6dC�dDdE�ZNG dFdG� dGe"jO�ZPdHZQe4ee4e4f ee4ee4 f e4dI�dJdK�ZRG dLdM� dMe!jS�ZTG dNdO� dOe*�ZUdS )Pa� Create a wheel that, when installed, will make the source package 'editable' (add it to the interpreter's path, including metadata) per PEP 660. Replaces 'setup.py develop'. .. note:: One of the mechanisms briefly mentioned in PEP 660 to implement editable installs is to create a separated directory inside ``build`` and use a .pth file to point to that directory. In the context of this file such directory is referred as *auxiliary build directory* or ``auxiliary_dir``. � N)�suppress)�Enum)�cleandoc)�chain)�Path)�TemporaryDirectory) � TYPE_CHECKING�Dict�Iterable�Iterator�List�Mapping�Optional�Tuple�TypeVar�Union� )�Command�_normalization�_path�errors� namespaces)�find_package_path)� Distribution)�InformationOnly� SetuptoolsDeprecationWarning�SetuptoolsWarning� )�build_py)� WheelFile)� � )�Protocol)�ABC�_P)Zboundc @ s4 e Zd ZdZdZdZdZeee d d�dd��Z dS ) � _EditableModea Possible editable installation modes: `lenient` (new files automatically added to the package - DEFAULT); `strict` (requires a new installation when files are added/removed); or `compat` (attempts to emulate `python setup.py develop` - DEPRECATED). �strictZlenient�compat)�mode�returnc C sN |s t jS |�� }|t jkr.t�d|�d���|dkrFtjdddd� t | S )NzInvalid editable mode: z. Try: 'strict'.�COMPATzCompat editable installsa The 'compat' editable mode is transitional and will be removed in future versions of `setuptools`. Please adapt your code accordingly to use either the 'strict' or the 'lenient' modes. z userguide/development_mode.html)Zsee_docs)r% �LENIENT�upper� __members__r � OptionErrorr �emit)�clsr( �_mode� r2 �I/tmp/pip-install-251nq386/setuptools/setuptools/command/editable_wheel.py�convertP s z_EditableMode.convertN) �__name__� __module__� __qualname__�__doc__�STRICTr+ r* � classmethodr �strr4 r2 r2 r2 r3 r% D s r% zU New or renamed files may not be automatically picked up without a new installation. zt Options like `package-data`, `include/exclude-package-data` or `packages.find.exclude/include` may have no effect. c @ s e Zd ZdZdZddddeejp"d�fgZdd � Zd d � Z d d � Z dd� Z dd� Z e e d�dd�Zeeeed�dd�Zdd� Zeee eeef f d�dd�Zeeeeeee eeef f d �d d �Zd d � Zed!�d"d#�Zd$d%� Zed&�d'd(�Zeeed)d*�d+d,�Z dS )-�editable_wheelz�Build 'editable' wheel for development. This command is private and reserved for internal use of setuptools, users should rely on ``setuptools.build_meta`` APIs. zBDO NOT CALL DIRECTLY, INTERNAL ONLY: create PEP 660 editable wheel)z dist-dir=�dz-directory to put final built distributions in)zdist-info-dir=�Iz(path to a pre-build .dist-info directoryzmode=N� c C s d | _ d | _d | _d | _d S )N)�dist_dir� dist_info_dir� project_dirr( )�selfr2 r2 r3 �initialize_options� s z!editable_wheel.initialize_optionsc C s@ | j }|jptj| _|jp i | _t| jp6tj� | jd��| _d S )N�dist) � distribution�src_root�os�curdirrB � package_dirr r@ �path�join)rC rE r2 r2 r3 �finalize_options� s z editable_wheel.finalize_optionsc C s� yD| j jdd� | �� | �d� | �d�}|�| j� | �|� W n< tk r� t � � | j j pl| j � � }tj|d� � Y nX d S )NT)�exist_ok� bdist_wheel)�project)r@ �mkdir�_ensure_dist_info�reinitialize_command�get_finalized_commandZwrite_wheelfilerA �_create_wheel_file� Exception� traceback� print_excrF �name�get_name�_DebuggingTipsr/ )rC rO rP r2 r2 r3 �run� s zeditable_wheel.runc C sb | j d kr6| �d�}| j|_|�� |�� |j | _ n(t| j ��d�sJt�t | j d�� � s^t�d S )N� dist_infoz .dist-info�METADATA) rA rS r@ � output_dir�ensure_finalizedr\ r; �endswith�AssertionErrorr �exists)rC r] r2 r2 r3 rR � s z editable_wheel._ensure_dist_infoc C sD | j }|jsd S t| j| j�dd���� }t||||�}|�� d S )Nr? �.) rF Znamespace_packagesr rB rJ �get�resolve�_NamespaceInstallerZinstall_namespaces)rC �installation_dirZ pth_prefixrE rG � installerr2 r2 r3 �_install_namespaces� s z"editable_wheel._install_namespaces)r) c C s2 | j rt| j �jnt� }tt|�d��}t|d �S )Nz *.egg-info)rA r �parent�mapr; �glob�next)rC � parent_dir� candidatesr2 r2 r3 �_find_egg_info_dir� s z!editable_wheel._find_egg_info_dir)rY �unpacked_wheel� build_lib�tmp_dirc C s | j }t|�}t|�}tt||� d�d��}tt||� d�d��}tt||� d�d��} |jddd�} t|�| _d| _|jddd�} |jd dd�} | | _ | _| _| | _ | _ | _ | | _ | _ || _|| _|�d �} d| _t|�| _|�d �}d |_| �� |_| �� | �� | �� d S )a� Configure commands to behave in the following ways: - Build commands can write to ``build_lib`` if they really want to... (but this folder is expected to be ignored and modules are expected to live in the project directory...) - Binary extensions should be built in-place (editable_mode = True) - Data/header/script files are not part of the "editable" specification so they are written directly to the unpacked_wheel directory. z.data�data�headers�scripts�egg_infoT)�reinit_subcommands�build�install�install_scriptsr FN)rF r; r rS Zegg_baseZignore_egg_info_in_manifest� build_platlib� build_purelibrs �install_purelib�install_platlib� install_libr| � build_scripts�install_headers� install_data�get_command_objZno_ep� build_temp�compilerq Zexisting_egg_info_dir�_set_editable_moder` )rC rY rr rs rt rE �wheelru rv rw rx rz r{ r| r r2 r2 r3 �_configure_build� s2 z editable_wheel._configure_buildc C sR | j }|�d�}x<|�� D ]0}|�|�}t|d�r:d|_qt|d�rd|_qW dS )z8Set the ``editable_mode`` flag in the build sub-commandsrz � editable_modeT�inplaceN)rF r� �get_sub_commands�hasattrr� r� )rC rE rz �cmd_name�cmdr2 r2 r3 r� � s z!editable_wheel._set_editable_modec C sn g }i }| � d�}xR|�� D ]F}| � |�}t|d�rF|�|�� pBg � t|d�r |�|�� p^i � q W ||fS )Nrz � get_outputs�get_output_mapping)rT r� r� �extendr� �updater� )rC �files�mappingrz r� r� r2 r2 r3 �_collect_build_outputs� s z%editable_wheel._collect_build_outputs)� dist_namerr rs rt r) c C sJ | � ||||� | �� | �� \}}| �d� | �d� | �d� ||fS )Nrv rw ru )r� �_run_build_subcommandsr� � _run_install)rC r� rr rs rt r� r� r2 r2 r3 �_run_build_commands s z"editable_wheel._run_build_commandsc C sT | � d�}xD|�� D ]8}| � |�}|dkrBt|�tkrB| �|� q| �|� qW dS )a} Issue #3501 indicates that some plugins/customizations might rely on: 1. ``build_py`` not running 2. ``build_py`` always copying files to ``build_lib`` However both these assumptions may be false in editable_wheel. This method implements a temporary workaround to support the ecosystem while the implementations catch up. rz r N)rT r� �type� build_py_cls� _safely_run� run_command)rC rz rY r� r2 r2 r3 r� s z%editable_wheel._run_build_subcommands)r� c C sH y | � |�S tk rB t�ddt�� � d|� d|� d�� Y nX d S )Nz0Customization incompatible with editable installz z� If you are seeing this warning it is very likely that a setuptools plugin or customization overrides the `a ` command, without taking into consideration how editable installs run build steps starting from setuptools v64.0.0. Plugin authors and developers relying on custom build steps are encouraged to update their `ab ` implementation considering the information about editable installs in https://setuptools.pypa.io/en/latest/userguide/extension.html. For the time being `setuptools` will silence this error and ignore the faulty command, but this behaviour will change in future versions. )r� rV r r/ rW � format_exc)rC r� r2 r2 r3 r� ( s zeditable_wheel._safely_runc C s> ddl m} | �d�}|j}d�|�� �}d}|� d|� d|� d�}t| j|�}|�� r`|� � t |d�} t dd�} t d d�} | ��} | ��} | ��}t| t| j �j�}t � | j |� | �| |j� | �|| | |�\}}| �||| �}|�2 ||d �� }||||� |�| � W d Q R X W d Q R X W d Q R X W d Q R X W d Q R X |S ) Nr )r r] �-z 0.editablez.whl)�suffixz .build-libz .build-temp�w)�wheel.wheelfiler rT rY rL Zget_tagr r@ rc �unlinkr rA �shutil�copytreerj r� �_select_strategyZ write_files)rC rO r r] r� �tag� build_tag� archive_name� wheel_pathrr rs Z build_tmpZunpacked�lib�tmpZunpacked_dist_infor� r� ZstrategyZ wheel_objr2 r2 r3 rU D s, <z!editable_wheel._create_wheel_file)�categoryc C sD t | jd|� �d �}|r@|� r@t�d|� d�� | �d|� �� d S )NZhas_z Installing z as non editable�install_)�getattrrF �_logger�infor� )rC r� Z has_categoryr2 r2 r3 r� ` s zeditable_wheel._run_install�EditableStrategy)rY r� rs r) c C s� d|� d|� �}t | j�}t�| j�}|tjkrRtt | jd|��}t| j|||�S t | j�}t || j |�} |tj k} t | j �dhkr�| s�| r�| j �dd�} t| j|t || �g�S t| j|�S )zDDecides which strategy to use to implement an editable installation.z __editable__.r� rz r? rd )r rB r% r4 r( r9 � _empty_dir� _LinkTreerF �_find_packages�_simple_layoutrJ r* �setre � _StaticPth�_TopLevelFinder) rC rY r� rs Z build_namerB r( � auxiliary_dir�packagesZhas_simple_layoutZis_compat_mode�src_dirr2 r2 r3 r� f s z editable_wheel._select_strategy) r5 r6 r7 r8 � descriptionr r% � user_optionsrD rM r\ rR rj r r; rq �_Pathr� r� r r r r� r� r� r� rU r� r� r2 r2 r2 r3 r< w s0 1 "" r< c @ s: e Zd Zdee eeef d�dd�Zdd� Zdd� Zd S ) r� r )r� r� r� c C s d S )Nr2 )rC r� r� r� r2 r2 r3 �__call__� s zEditableStrategy.__call__c C s d S )Nr2 )rC r2 r2 r3 � __enter__� s zEditableStrategy.__enter__c C s d S )Nr2 )rC � _exc_type� _exc_value� _tracebackr2 r2 r3 �__exit__� s zEditableStrategy.__exit__N) r5 r6 r7 r r; r r� r� r� r2 r2 r2 r3 r� � s r� c @ sP e Zd Zeeee d�dd�Zdee eeef d�dd�Z dd � Z d d � Z d S ) r� )rE rY � path_entriesc C s || _ || _|| _d S )N)rE rY r� )rC rE rY r� r2 r2 r3 �__init__� s z_StaticPth.__init__r )r� r� r� c C s@ d� dd� | jD ��}t|� d�d�}|�d| j� d�|� d S )N� c s s | ]}t |�� �V qd S )N)r; rf )�.0�pr2 r2 r3 � <genexpr>� s z&_StaticPth.__call__.<locals>.<genexpr>zutf-8z __editable__.z.pth)rL r� �bytes�writestrrY )rC r� r� r� �entries�contentsr2 r2 r3 r� � s z_StaticPth.__call__c C s, dt ttj| j���d�}t�|t � | S )Nz_ Editable install will be performed using .pth file to extend `sys.path` with: z )�listrl rH �fspathr� r� �warning�_LENIENT_WARNING)rC �msgr2 r2 r3 r� � s z_StaticPth.__enter__c C s d S )Nr2 )rC r� r� r� r2 r2 r3 r� � s z_StaticPth.__exit__N) r5 r6 r7 r r; r r r� r r� r� r� r2 r2 r2 r3 r� � s r� c s� e Zd ZdZeeeed�� fdd� Zdee e eef d�� fdd� Z ee e d �d d �Z deed �dd�Z dd� Zdd� Zdd� Z� ZS )r� a` Creates a ``.pth`` file that points to a link tree in the ``auxiliary_dir``. This strategy will only link files (not dirs), so it can be implemented in any OS, even if that means using hardlinks instead of symlinks. By collocating ``auxiliary_dir`` and the original source code, limitations with hardlinks should be avoided. )rE rY r� rs c s> t |�| _t |��� | _|�d�j| _t� �||| jg� d S )Nr ) r r� rf rs r� � copy_file�_file�superr� )rC rE rY r� rs )� __class__r2 r3 r� � s z_LinkTree.__init__r )r� r� r� c s | � ||� t� �|||� d S )N)� _create_linksr� r� )rC r� r� r� )r� r2 r3 r� � s z_LinkTree.__call__)�filer) c C s: t t��( t|��� �| j�}t|��tj d�S Q R X d S )N�/) r � ValueErrorr rf Z relative_tors r; �replacerH �sep)rC r� rK r2 r2 r3 �_normalize_output� s z_LinkTree._normalize_outputN)�relative_output�src_filec C s6 | j | }|j�� s"|jjdd� | j|||d� d S )NT)�parents)�link)r� rk �is_dirrQ r� )rC r� r� r� �destr2 r2 r3 � _create_file� s z_LinkTree._create_filec s� � j jddd� t� j �r dnd}� fdd�|�� D �}|�d d � x.|D ]&}� �|�}|rJ||krJ� �||� qJW x$|�� D ]\}}� j|||d� q~W d S )NT)r� rN �sym�hardc s i | ]\}}|� � |��qS r2 )r� )r� �k�v)rC r2 r3 � <dictcomp>� s z+_LinkTree._create_links.<locals>.<dictcomp>)r� )r� rQ �_can_symlink_files�items�popr� r� )rC �outputsZoutput_mappingZ link_typeZmappings�outputZrelative�srcr2 )rC r3 r� � s z_LinkTree._create_linksc C s d}t �|t � | S )Nz=Strict editable install will be performed using a link tree. )r� r� �_STRICT_WARNING)rC r� r2 r2 r3 r� � s z_LinkTree.__enter__c C s d| j � d�}t�d|� d S )Nz\ Strict editable installation performed using the auxiliary directory: z� Please be careful to not remove this directory, otherwise you might not be able to import/use your package. zEditable installation.)r� r r/ )rC r� r� r� r� r2 r2 r3 r� � s z_LinkTree.__exit__)N)r5 r6 r7 r8 r r; r� r� r r r� r r� r� r� r� r� � __classcell__r2 r2 )r� r3 r� � s "r� c @ sJ e Zd Zeed�dd�Zdee eeef d�dd�Zdd � Z d d � Z d S ) r� )rE rY c C s || _ || _d S )N)rE rY )rC rE rY r2 r2 r3 r� � s z_TopLevelFinder.__init__r )r� r� r� c C s� | j jp tj}tt| j �t| j ��}| j jp.i }t|||�}t tt | j j pLg |�dd� t |�D ���}d| j � d�} t�| �} tt| ||�d�} |�| � d�| � td| � d| � d �d�} |�d| j � d �| � d S ) Nc s s | ]}|g fV qd S )Nr2 )r� �nsr2 r2 r3 r� � s z+_TopLevelFinder.__call__.<locals>.<genexpr>z __editable__.z.finderzutf-8z.pyzimport z; z .install()z.pth)rE rG rH rI r r� �_find_top_level_modulesrJ �_find_package_roots�dict�_find_namespacesr� �_find_virtual_namespacesrY r Zsafe_identifierr� �_finder_templater� ) rC r� r� r� rG Z top_levelrJ �rootsZ namespaces_rY �finder�contentr2 r2 r3 r� � s z_TopLevelFinder.__call__c C s d}t �|t � | S )Nz=Editable install will be performed using a meta path finder. )r� r� r� )rC r� r2 r2 r3 r� s z_TopLevelFinder.__enter__c C s d}t �d|� d S )Nz� Please be careful with folders in your working directory with the same name as your package as they may take precedence during imports. zEditable installation.)r r/ )rC r� r� r� r� r2 r2 r3 r� s z_TopLevelFinder.__exit__N) r5 r6 r7 r r; r� r r r� r� r� r2 r2 r2 r3 r� � s r� )�base_dirr) c C s� t t| �� �d���}t|d�t|d� }}|jddd� tttt��. t � ||� |� � rn|j dd�dkrndS W d Q R X yt � ||� W n0 tk r� } zd}t|�|�W d d }~X Y nX d S Q R X d S ) N)�dirz file1.txtz file2.txt�file1zutf-8)�encodingTz�File system does not seem to support either symlinks or hard links. Strict editable installs require one of them to be supported.F)r r; rf r Z write_textr �AttributeError�NotImplementedError�OSErrorrH �symlink� is_symlinkZ read_textr� rV �LinksNotSupported)r r� �path1�path2�exr� r2 r2 r3 r� s r� )r� rJ rB r) c s^ � �fdd�| D �}|s*t � �i dhfkS tj�dd� |�� D ���t�fdd�|�� D ��S )a[ Return ``True`` if: - all packages are contained by the same parent directory, **and** - all packages become importable if the parent directory is added to ``sys.path``. >>> _simple_layout(['a'], {"": "src"}, "/tmp/myproj") True >>> _simple_layout(['a', 'a.b'], {"": "src"}, "/tmp/myproj") True >>> _simple_layout(['a', 'a.b'], {}, "/tmp/myproj") True >>> _simple_layout(['a', 'a.a1', 'a.a1.a2', 'b'], {"": "src"}, "/tmp/myproj") True >>> _simple_layout(['a', 'a.a1', 'a.a1.a2', 'b'], {"a": "a", "b": "b"}, ".") True >>> _simple_layout(['a', 'a.a1', 'a.a1.a2', 'b'], {"a": "_a", "b": "_b"}, ".") False >>> _simple_layout(['a', 'a.a1', 'a.a1.a2', 'b'], {"a": "_a"}, "/tmp/myproj") False >>> _simple_layout(['a', 'a.a1', 'a.a1.a2', 'b'], {"a.a1.a2": "_a2"}, ".") False >>> _simple_layout(['a', 'a.b'], {"": "src", "a.b": "_ab"}, "/tmp/myproj") False >>> # Special cases, no packages yet: >>> _simple_layout([], {"": "src"}, "/tmp/myproj") True >>> _simple_layout([], {"a": "_a", "": "src"}, "/tmp/myproj") False c s i | ]}t |� ��|�qS r2 )r )r� �pkg)rJ rB r2 r3 r� B s z"_simple_layout.<locals>.<dictcomp>r? c S s g | ]\}}t ||��qS r2 )� _parent_path)r� r� r� r2 r2 r3 � <listcomp>H s z"_simple_layout.<locals>.<listcomp>c 3 s. | ]&\}}t �t� f|�d ��� |�V qdS )rd N)r Z same_pathr �split)r� �key�value)rk r2 r3 r� J s z!_simple_layout.<locals>.<genexpr>)r� rH rK � commonpathr� �all)r� rJ rB Zlayoutr2 )rJ rk rB r3 r� # s r� c C s0 |� | �r |dt| � � n|}|�dtj �S )a7 Infer the parent path containing a package, that if added to ``sys.path`` would allow importing that package. When ``pkg`` is directly mapped into a directory with a different name, return its own path. >>> _parent_path("a", "src/a") 'src' >>> _parent_path("b", "src/c") 'src/c' Nr� )ra �len�rstriprH r� )r �pkg_pathrk r2 r2 r3 r O s r )rE r) c c s� t | jp g �E d H | jp g }dd� |D �}| jr<| jV n | jpDg }|dd� |D �7 }x"|D ]}|�d�\}}}|V q^W d S )Nc S s g | ]}d |kr|�qS )rd r2 )r� �modr2 r2 r3 r a s z"_find_packages.<locals>.<listcomp>c S s g | ]}d |j kr|j �qS )rd )rY )r� �xr2 r2 r3 r f s rd )�iterr� � py_modules� ext_package� ext_modules� rpartition)rE r Znested_modulesr �module�package�_r2 r2 r3 r� ] s r� c c sF | j pg }dd� |D �E d H | jsB| jp,g }dd� |D �E d H d S )Nc s s | ]}d |kr|V qdS )rd Nr2 )r� r r2 r2 r3 r� o s z*_find_top_level_modules.<locals>.<genexpr>c s s | ]}d |j kr|j V qdS )rd N)rY )r� r r2 r2 r3 r� s s )r r r )rE r r r2 r2 r3 r� m s r� )r� rJ rG r) c s � �fdd�t | �D �}t|�S )Nc s i | ]}t t|� ���|�qS r2 )�_absolute_rootr )r� r )rJ rG r2 r3 r� { s z'_find_package_roots.<locals>.<dictcomp>)�sorted�_remove_nested)r� rJ rG � pkg_rootsr2 )rJ rG r3 r� v s r� )rK r) c C s8 t | �}|j}|�� r"t|�� �S t|�� |j �S dS )z(Works for packages and top-level modulesN)r rk rc r; rf rY )rK �path_rk r2 r2 r3 r" � s r" )r% r) c c s| xv| D ]n}d|krq|� d�}xTtt|�d dd�D ]<}d�|d|� �}tt|| d��}|�� rj|| kr4|V q4W qW dS )a8 By carefully designing ``package_dir``, it is possible to implement the logical structure of PEP 420 in a package without the corresponding directories. Moreover a parent package can be purposefully/accidentally skipped in the discovery phase (e.g. ``find_packages(include=["mypkg.*"])``, when ``mypkg.foo`` is included by ``mypkg`` itself is not). We consider this case to also be a virtual namespace (ignoring the original directory) to emulate a non-editable installation. This function will try to find these kinds of namespaces. rd r r ���Nr? )r �ranger rL r r rc )r% r �parts�iZ partial_namerK r2 r2 r3 r� � s r� )r� r% r) c c sD x>| D ]6}t ||d�}t|��� rt|d��� s||gfV qW d S )Nr? z __init__.py)r r rc )r� r% r rK r2 r2 r3 r� � s r� c sT t | �� �}xBtt| �� ��D ].\�� t� �fdd�| �� D ��r |��� q W |S )Nc 3 s( | ] \}}�|ko t �� ||�V qd S )N)� _is_nested)r� �otherZ other_path)rK r r2 r3 r� � s z!_remove_nested.<locals>.<genexpr>)r� �copy�reversedr� r� �anyr� )r% r� r2 )rK r r3 r$ � s r$ )r r rk � parent_pathr) c C sF t �|�}| �|dd��d��d�}| �|�oD|t �t|f|�� �kS )a� Return ``True`` if ``pkg`` is nested inside ``parent`` both logically and in the file system. >>> _is_nested("a.b", "path/a/b", "a", "path/a") True >>> _is_nested("a.b", "path/a/b", "a", "otherpath/a") False >>> _is_nested("a.b", "path/a/b", "c", "path/c") False >>> _is_nested("a.a", "path/a/a", "a", "path/a") True >>> _is_nested("b.a", "path/b/a", "a", "path/a") False r? r rd )r �normpathr� �stripr � startswithr )r r rk r0 Z norm_pkg_path�restr2 r2 r3 r+ � s r+ )�dir_r) c C s t j| dd� t�| � | S )zFCreate a directory ensured to be empty. Existing files may be removed.T)� ignore_errors)r� �rmtreerH �makedirs)r5 r2 r2 r3 r� � s r� c @ s$ e Zd Zdd� Zdd� Zdd� ZdS )rg c C s( || _ || _|| _|| _g | _d| _d S )NF)rF rG rh � editable_namer� �dry_run)rC rF rh r9 rG r2 r2 r3 r� � s z _NamespaceInstaller.__init__c C s t j�| j| j�S )zInstallation target.)rH rK rL rh r9 )rC r2 r2 r3 � _get_target� s z _NamespaceInstaller._get_targetc C s t t| j��S )z1Where the modules/packages should be loaded from.)�reprr; rG )rC r2 r2 r3 � _get_root� s z _NamespaceInstaller._get_rootN)r5 r6 r7 r� r; r= r2 r2 r2 r3 rg � s rg a< import sys from importlib.machinery import ModuleSpec from importlib.machinery import all_suffixes as module_suffixes from importlib.util import spec_from_file_location from itertools import chain from pathlib import Path MAPPING = {mapping!r} NAMESPACES = {namespaces!r} PATH_PLACEHOLDER = {name!r} + ".__path_hook__" class _EditableFinder: # MetaPathFinder @classmethod def find_spec(cls, fullname, path=None, target=None): for pkg, pkg_path in reversed(list(MAPPING.items())): if fullname == pkg or fullname.startswith(f"{{pkg}}."): rest = fullname.replace(pkg, "", 1).strip(".").split(".") return cls._find_spec(fullname, Path(pkg_path, *rest)) return None @classmethod def _find_spec(cls, fullname, candidate_path): init = candidate_path / "__init__.py" candidates = (candidate_path.with_suffix(x) for x in module_suffixes()) for candidate in chain([init], candidates): if candidate.exists(): return spec_from_file_location(fullname, candidate) class _EditableNamespaceFinder: # PathEntryFinder @classmethod def _path_hook(cls, path): if path == PATH_PLACEHOLDER: return cls raise ImportError @classmethod def _paths(cls, fullname): # Ensure __path__ is not empty for the spec to be considered a namespace. return NAMESPACES[fullname] or MAPPING.get(fullname) or [PATH_PLACEHOLDER] @classmethod def find_spec(cls, fullname, target=None): if fullname in NAMESPACES: spec = ModuleSpec(fullname, None, is_package=True) spec.submodule_search_locations = cls._paths(fullname) return spec return None @classmethod def find_module(cls, fullname): return None def install(): if not any(finder == _EditableFinder for finder in sys.meta_path): sys.meta_path.append(_EditableFinder) if not NAMESPACES: return if not any(hook == _EditableNamespaceFinder._path_hook for hook in sys.path_hooks): # PathEntryFinder is needed to create NamespaceSpec without private APIS sys.path_hooks.append(_EditableNamespaceFinder._path_hook) if PATH_PLACEHOLDER not in sys.path: sys.path.append(PATH_PLACEHOLDER) # Used just to trigger the path hook )rY r� r r) c C s( t t|�� dd� d��}tj| ||d�S )z_Create a string containing the code for the``MetaPathFinder`` and ``PathEntryFinder``. c S s | d S )Nr r2 )r� r2 r2 r3 �<lambda>: � z"_finder_template.<locals>.<lambda>)r )rY r� r )r� r# r� �_FINDER_TEMPLATE�format)rY r� r r2 r2 r3 r� 4 s r� c @ s e Zd ZdZdS )r zCFile system does not seem to support either symlinks or hard links.N)r5 r6 r7 r8 r2 r2 r2 r3 r > s r c @ s e Zd ZdZdZdZdS )r[ z!Problem in editable installation.a An error happened while installing `{project}` in editable mode. The following steps are recommended to help debug this problem: - Try to install the project normally, without using the editable mode. Does the error still persist? (If it does, try fixing the problem before attempting the editable mode). - If you are using binary extensions, make sure you have all OS-level dependencies installed (e.g. compilers, toolchains, binary libraries, ...). - Try the latest version of setuptools (maybe the error was already fixed). - If you (or your project dependencies) are using any setuptools extension or customization, make sure they support the editable mode. After following the steps above, if the problem still persists and you think this is related to how setuptools handles editable installations, please submit a reproducible example (see https://stackoverflow.com/help/minimal-reproducible-example) to: https://github.com/pypa/setuptools/issues z userguide/development_mode.htmlN)r5 r6 r7 Z_SUMMARYZ_DETAILSZ _SEE_DOCSr2 r2 r2 r3 r[ B s r[ )Vr8 �loggingrH r� �sysrW � contextlibr �enumr �inspectr � itertoolsr Zpathlibr �tempfiler �typingr r r r r r r r r r r? r r r r r Z discoveryr rE r �warningsr r r r r� r� r � version_infor" Ztyping_extensions�abcr# r; r� r$ � getLoggerr5 r� r% r� r� r< r� r� r� r� �boolr� r� r r� r� r� r" r� r� r$ r+ r� � Installerrg r@ r� Z FileErrorr r[ r2 r2 r2 r3 �<module> sx 0 + G%* W
| ver. 1.4 |
Github
|
.
| PHP 8.3.23 | Генерация страницы: 0.03 |
proxy
|
phpinfo
|
Настройка