File manager - Edit - /opt/saltstack/salt/lib/python3.10/site-packages/setuptools/command/__pycache__/editable_wheel.cpython-310.pyc
Back
o ;j.� � @ s� d Z ddlmZ ddlZddlZddlZddlZddlZddlZddl m Z m Z m Z ddl mZ ddlmZ ddlmZ ddlmZmZ dd lmZ dd lmZ dd lmZ dd l m Z m Z m Z m Z d dl!m"Z"m#Z#m$Z$m%Z%m&Z&m'Z' d dl$m(Z( d dl)m*Z*m+Z+ d dl,m-Z- d dl.m/Z/ d dl0m1Z1m2Z2 ddl3m3Z4 ddl5m5Z6 ddl7m7Z8 ddl9m9Z: ddl;m;Z< ddl=m=Z> e r�ddl?m@Z@ d d lAmBZB e d e(d �ZCe�DeE�ZFG d d � d e�ZGd!ZHd"ZIG d#d$� d$e"�ZJG d%d&� d&e �ZKG d'd(� d(�ZLG d)d*� d*eL�ZMG d+d,� d,�ZNdmd1d2�ZOdnd6d7�ZPdod>d?�ZQd@dA� ZRdpdEdF�ZSdpdGdH�ZTdqdKdL�ZUdrdNdO�ZVdsdQdR�ZWdtdUdV�ZXdudWdX�ZYdvd]d^�ZZdwd`da�Z[G dbdc� dce'j\�Z]ddZ^dxdidj�Z_G dkdl� dle&j`�ZadS )ya� 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``. � )� annotationsN)�Iterable�Iterator�Mapping)�suppress)�Enum)�cleandoc)�chain�starmap)�Path)�TemporaryDirectory)� TracebackType)� TYPE_CHECKING�Protocol�TypeVar�cast� )�Command�_normalization�_path�_shutil�errors� namespaces)�StrPath)�py310�py312��find_package_path)� Distribution)�InformationOnly� SetuptoolsDeprecationWarning� )�build)�build_py)� dist_info)�egg_info)�install)�install_scripts)�Self�� WheelFile�_P)�boundc @ s* e Zd ZdZdZdZdZed dd ��Zd S ) � _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� str | None�returnc C sN |st jS |�� }|t jvrt�d|�d���|dkr#tjdddd� 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 Z OptionErrorr �emit)�clsr0 �_mode� r: �U/opt/saltstack/salt/lib/python3.10/site-packages/setuptools/command/editable_wheel.py�convertA s �z_EditableMode.convertN)r0 r1 r2 r- ) �__name__� __module__� __qualname__�__doc__�STRICTr4 r3 � classmethodr< r: r: r: r; r- 5 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 ZdZdZddddeejpd�fgZdd � Zd5d d �Z d5dd�Z dd� Z dd� Z d6dd�Z d7d d �Zd d � Zd8d"d#�Zd9d%d&�Zd5d'd(�Zd:d*d+�Zd,d-� Zd;d/d0�Zd<d3d4�ZdS )=�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_dirr0 ��selfr: r: r; �initialize_optionsv s z!editable_wheel.initialize_optionsr2 �Nonec C s@ | j }|jptj| _|jpi | _t| jptj� | jd��| _d S )N�dist) � distribution�src_root�os�curdirrJ � package_dirr rH �path�join)rL rO r: r: r; �finalize_options| s z editable_wheel.finalize_optionsc C s� z#| j jdd� | �� | �d� | �d�}|�| j� | �|� W d S tyC } z| j j p3| j � � }t � |d|� d�� � d }~ww )NT)�exist_ok� bdist_wheelz3An error occurred when building editable wheel for zl. See debugging tips in: https://setuptools.pypa.io/en/latest/userguide/development_mode.html#debugging-tips)rH �mkdir�_ensure_dist_info�reinitialize_command�get_finalized_commandZwrite_wheelfilerI �_create_wheel_file� ExceptionrP �name�get_namer Zadd_note)rL rY �exZprojectr: r: r; �run� s ���zeditable_wheel.runc C sj | j d u r tt| �d��}| j|_|�� |�� |j | _ d S t| j �� d�s)J �t | j d�� � s3J �d S )Nr$ z .dist-infoZMETADATA) rI r � dist_info_clsr\ rH Z output_dir�ensure_finalizedrc �str�endswithr �exists)rL r$ r: r: r; r[ � s z editable_wheel._ensure_dist_infoc C sD | j }|jsd S t| j| j�dd���� }t||||�}|�� d S )NrF �.) rP �namespace_packagesr rJ rT �get�resolve�_NamespaceInstallerZinstall_namespaces)rL �installation_dirZ pth_prefixrO rQ Z installerr: r: r; �_install_namespaces� s z"editable_wheel._install_namespacesr1 c C s2 | j r t| j �jnt� }tt|�d��}t|d �S )Nz *.egg-info)rI r �parent�maprf �glob�next)rL Z parent_dirZ candidatesr: r: r; �_find_egg_info_dir� s z!editable_wheel._find_egg_info_dirr` rf �unpacked_wheelr � build_lib�tmp_dirc C sL | j }t|�}t|�}tt||� d�d��}tt||� d�d��}tt||� d�d��} tt|jddd��} t|�| _d| _tt|jddd��} tt |jd dd��} | | _ | _ | _ | | _ | _| _| | _| _|| _|| _|�d �} d | _tt|�d ��}d|_t|�| _tt|�d ��}d|_| �� |_ | � � | � � | � � dS )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�scriptsr% T)Zreinit_subcommandsr" r& � build_scripts�pythonr' r# FN) rP rf r r � egg_info_clsr\ Zegg_baseZignore_egg_info_in_manifest� build_cls� install_clsZ build_platlibZ build_purelibrv Zinstall_purelibZinstall_platlibZ install_libr' r{ Zinstall_headersZ install_data�get_command_obj� executable�install_scripts_clsZno_epZ build_temp� build_py_cls�compilert Zexisting_egg_info_dir�_set_editable_modere )rL r` ru rv rw rO �wheelrx ry rz r% r" r& r{ r' r# r: r: r; �_configure_build� sF � �� � z editable_wheel._configure_buildc C sN | j }|�d�}|�� D ]}|�|�}t|d�r d|_q t|d�r$d|_q dS )z8Set the ``editable_mode`` flag in the build sub-commandsr" � editable_modeT�inplaceN)rP r� �get_sub_commands�hasattrr� r� )rL rO r" �cmd_name�cmdr: r: r; r� � s ��z!editable_wheel._set_editable_mode� tuple[list[str], dict[str, str]]c C sj g }i }| � d�}|�� D ]#}| � |�}t|d�r"|�|�� p g � t|d�r0|�|�� p.i � q ||fS )Nr" � get_outputs�get_output_mapping)r] r� r� �extendr� �updater� )rL �files�mappingr" r� r� r: r: r; �_collect_build_outputs� s �z%editable_wheel._collect_build_outputs� dist_namec C sJ | � ||||� | �� | �� \}}| �d� | �d� | �d� ||fS )Nry rz rx )r� �_run_build_subcommandsr� � _run_install)rL r� ru rv rw r� r� r: r: r; �_run_build_commands s z"editable_wheel._run_build_commandsc C sP | � d�}|�� D ] }| � |�}|dkr t|�tur | �|� q | �|� q 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. r" r# N)r] r� �typer� � _safely_run� run_command)rL r" r` r� r: r: r; r� s �z%editable_wheel._run_build_subcommandsr� c C sF z| � |�W S ty" t�ddt�� � d|� d|� d�� Y d S w )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 `aa ` 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 behavior will change in future versions. )r� r_ r r7 � traceback� format_exc)rL r� r: r: r; r� . s �� � ��zeditable_wheel._safely_runc C s� ddl m} | �d�}|j}d�|�� �}d}|� d|� d|� d�}t| j|�}|�� r0|� � t |d�} t dd�} t d d�} | ��} | �s} | �a}t| t| j �j�}t � | j |� | �| |� | �|| | |�\}}| �||| �}|�( ||d ��}||||� |�| � W d � n1 s�w Y W d � n1 s�w Y W d � n1 s�w Y W d � n1 s�w Y W d � |S W d � |S 1 s�w Y |S ) Nr r) r$ �-z 0.editablez.whl)�suffixz .build-libz .build-temp�w)Zwheel.wheelfiler* r] r` rV Zget_tagr rH rh �unlinkr rI �shutil�copytreero r� �_select_strategyZ write_files)rL rY r* r$ r� �tagZ build_tag� archive_name� wheel_pathru rv Z build_tmpZunpacked�lib�tmpZunpacked_dist_infor� r� ZstrategyZ wheel_objr: r: r; r^ J sB �� � ��( � � z!editable_wheel._create_wheel_file�categoryc C sL t | jd|� �d �}|r"|� r$t�d|� d�� | �d|� �� d S d S d S )NZhas_z Installing z as non editableZinstall_)�getattrrP �_logger�infor� )rL r� Z has_categoryr: r: r; r� f s �zeditable_wheel._run_installr� �EditableStrategyc C s� d|� d|� �}t | j�}t�| j�}|tju r)tt | jd|��}t| j|||�S t | j�}t || j |�} |tj u } t | j �dhkrD| sF| rX| j �dd�} t| j|t || �g�S t| j|�S )zDDecides which strategy to use to implement an editable installation.� __editable__.r� r" rF ri )r rJ r- r< r0 rA � _empty_dir� _LinkTreerP �_find_packages�_simple_layoutrT r3 �setrk � _StaticPth�_TopLevelFinder) rL r` r� rv Z build_namerJ r0 � auxiliary_dir�packagesZhas_simple_layoutZis_compat_modeZsrc_dirr: r: r; r� l s z editable_wheel._select_strategy�r2 rN )r2 r1 )r` rf ru r rv r rw r )r2 r� ) r� rf ru r rv r rw r r2 r� )r� rf )r� rf )r` rf r� rf rv r r2 r� )r= r> r? r@ � descriptionr r- Z user_optionsrM rW rc r[ ro rt r� r� r� r� r� r� r^ r� r� r: r: r: r; rC h s, � ? rC c @ s* e Zd Zdd d �Zdd d �Zddd�ZdS )r� r� r* r� � list[str]r� �Mapping[str, str]r2 �objectc C � d S rG r: �rL r� r� r� r: r: r; �__call__� s zEditableStrategy.__call__r( c C r� rG r: rK r: r: r; � __enter__� s zEditableStrategy.__enter__� _exc_type�type[BaseException] | None� _exc_value�BaseException | None� _traceback�TracebackType | Nonec C r� rG r: �rL r� r� r� r: r: r; �__exit__� s zEditableStrategy.__exit__N)r� r* r� r� r� r� r2 r� �r2 r( )r� r� r� r� r� r� r2 r� )r= r> r? r� r� r� r: r: r: r; r� � s r� c @ s4 e Zd Zd d d �Zd dd�Zd dd�Zd dd�Zd S )!r� rO r r` rf � path_entries� list[Path]r2 rN c C s || _ || _|| _d S rG )rO r` r� )rL rO r` r� r: r: r; �__init__� s z_StaticPth.__init__r� r* r� r� r� r� c C s> d� dd� | jD ��}t|� d��}|�d| j� d�|� d S )N� c s s � | ] }t |�� �V qd S rG )rf rl )�.0�pr: r: r; � <genexpr>� � � z&_StaticPth.__call__.<locals>.<genexpr>r� �.pth)rV r� � _encode_pth�writestrr` )rL r� r� r� �entries�contentsr: r: r; r� � s z_StaticPth.__call__r( 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 )�listrq rR �fspathr� r� �warning�_LENIENT_WARNING�rL �msgr: r: r; r� � s �z_StaticPth.__enter__r� r� r� r� c C r� rG r: r� r: r: r; r� � s z_StaticPth.__exit__N)rO r r` rf r� r� r2 rN �r� r* r� r� r� r� r2 rN r� �r� r� r� r� r� r� r2 rN )r= r> r? r� r� r� r� r: r: r: r; r� � s r� c sd e Zd ZdZd*� fd d � Zd+� fdd� Zd,dd�Zd-d.d d �Zd/d d �Zd0d"d#�Z d1d(d)�Z � Z S )2r� 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. rO r r` rf r� r rv r2 rN c s> t |�| _t |��� | _|�d�j| _t� �||| jg� d S )Nr# ) r r� rl rv r� Z copy_file�_file�superr� )rL rO r` r� rv �� __class__r: r; r� � s z_LinkTree.__init__r� r* r� r� r� r� c s | � ||� t� �|||� d S rG )� _create_linksr� r� r� r� r: r; r� � s z_LinkTree.__call__�filer1 c C sR t t�� t|��� �| j�}t|��tj d�W d � S 1 s"w Y d S )N�/) r � ValueErrorr rl � relative_torv rf �replacerR �sep)rL r� rU r: r: r; �_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� rp �is_dirrZ r� )rL r� r� r� �destr: r: r; � _create_file� s z_LinkTree._create_file�output_mappingc s� � j jddd� t� j �rdnd}� fdd�|�� D �}dd� |D �}|D ]}� �|�}|r8||vr8� �||� q%|�� D ] \}}� j|||d � q=d S ) NT)r� rX ZsymZhardc 3 s" � | ] \}}� � |�|fV qd S rG )r� �r� �k�vrK r: r; r� � s � z*_LinkTree._create_links.<locals>.<genexpr>c S s i | ] \}}|d ur||�qS rG r: r� r: r: r; � <dictcomp>� s z+_LinkTree._create_links.<locals>.<dictcomp>r� )r� rZ �_can_symlink_files�itemsr� r� ) rL �outputsr� Z link_typeZ normalisedZmappings�outputZrelative�srcr: rK r; r� � s ��z_LinkTree._create_linksr( c C � d}t �|t � | S )Nz=Strict editable install will be performed using a link tree. )r� r� �_STRICT_WARNINGr� r: r: r; r� � � z_LinkTree.__enter__r� r� r� r� 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. �Editable installation.)r� r r7 �rL r� r� r� r� r: r: r; r� � s �z_LinkTree.__exit__) rO r r` rf r� r rv r r2 rN r� )r� rf r2 r1 rG )r� rf r� rf )r� r� r� r� ) r= r> r? r@ r� r� r� r� r� r� r� � __classcell__r: r: r� r; r� � s r� c @ sH e Zd Zd!dd�Zd"d d �Zd#d d�Zd$dd�Zd%dd�Zd&d d �Zd S )'r� rO r r` rf r2 rN c C s || _ || _d S rG )rO r` )rL rO r` r: r: r; r� s z_TopLevelFinder.__init__�5tuple[str, str, dict[str, str], dict[str, list[str]]]c s� �j jptj}tt�j �t�j ��}�j jpi }t|||�� t tt �j j p&g � �dd� t � �D ���}� �fdd��j j p>g D �}i � �|�}d�j� d�}t�|�}||||fS )Nc s s � | ]}|g fV qd S rG r: )r� �nsr: r: r; r� s � z0_TopLevelFinder.template_vars.<locals>.<genexpr>c s" i | ] }|t |� �jjp d ��qS )rF )r rO rQ �r� �pkg��rootsrL r: r; r� s ��z1_TopLevelFinder.template_vars.<locals>.<dictcomp>r� z.finder)rO rQ rR rS r r� �_find_top_level_modulesrT �_find_package_roots�dict�_find_namespacesr� �_find_virtual_namespacesrj r` r Zsafe_identifier) rL rQ Z top_levelrT � namespaces_Zlegacy_namespacesr� r` �finderr: r r; � template_vars s" �� � z _TopLevelFinder.template_vars�Iterator[tuple[str, bytes]]c c sb � | � � \}}}}tt|||�d�}|� d�|fV td|� d|� d��}d| j� d�|fV d S )N�utf-8z.pyzimport z; z .install()r� r� )r �bytes�_finder_templater� r` )rL r r` r� r �contentr: r: r; �get_implementation s �z"_TopLevelFinder.get_implementationr� r* r� r� r� r� c C s" | � � D ] \}}|�||� qd S rG )r r� )rL r� r� r� r� r r: r: r; r� ) s �z_TopLevelFinder.__call__r( c C r� )Nz=Editable install will be performed using a meta path finder. )r� r� r� r� r: r: r; r� / r z_TopLevelFinder.__enter__r� r� r� r� 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. r )r r7 r r: r: r; r� 4 s z_TopLevelFinder.__exit__N)rO r r` rf r2 rN )r2 r )r2 r r� r� r� ) r= r> r? r� r r r� r� r� r: r: r: r; r� s r� r rf r2 r c C s` t �� �"}t j|tjd�}|�| � |�� |�d� |�� W d � S 1 s)w Y dS )a� Prior to Python 3.13 (see https://github.com/python/cpython/issues/77102), .pth files are always read with 'locale' encoding, the recommendation from the cpython core developers is to write them as ``open(path, "w")`` and ignore warnings (see python/cpython#77102, pypa/setuptools#3937). This function tries to simulate this behavior without having to create an actual file, in a way that supports a range of active Python versions. (There seems to be some variety in the way different version of Python handle ``encoding=None``, not all of them use ``locale.getpreferredencoding(False)`` or ``locale.getencoding()``). ��encodingr N) �io�BytesIO� TextIOWrapperr Z PTH_ENCODING�write�flush�seek�read)r �buffer�wrapperr: r: r; r� A s $�r� �base_dirr �boolc C s t t| �� �d��o}t|d�t|d�}}|jddd� tttt��) t � ||� |� � rD|j dd�dkrD W d � W d � dS W d � n1 sNw Y zt � ||� W n tyn } zd}t|�|�d }~ww W d � d S 1 s{w Y d S ) N)�dirz file1.txtz file2.txtZfile1r r Tz�File system does not seem to support either symlinks or hard links. Strict editable installs require one of them to be supported.F)r rf rl r � write_textr �AttributeError�NotImplementedError�OSErrorrR �symlink� is_symlink� read_textr� r_ �LinksNotSupported)r$ r� Zpath1Zpath2rb r� r: r: r; r� V s* ��� � ��$�r� r� � Iterable[str]rT �dict[str, str]rJ r c sZ � �fdd�| D �}|st � �i dhfv S tj�tt|�� ���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 r: r r )rT rJ r: r; r� � s z"_simple_layout.<locals>.<dictcomp>rF c 3 s2 � | ]\}}t �t� g|�d ��R � |�V qdS �ri N)r Z same_pathr �split)r� �key�value)rp r: r; r� � s � � �z!_simple_layout.<locals>.<genexpr>)r� rR rU � commonpathr � _parent_pathr� �all)r� rT rJ Zlayoutr: )rT rp rJ r; r� j s �r� c C s |� | �}|�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' r� )� removesuffix�rstriprR r� )r �pkg_pathrp r: r: r; r6 � s r6 rO r � Iterator[str]c c s~ � t | jpg �E d H | jpg }dd� |D �}| jr | jV n| jp#g }|dd� |D �7 }|D ] }|�d�\}}}|V q/d S )Nc S s g | ]}d |v r|�qS �ri r: �r� �modr: r: r; � <listcomp>� s z"_find_packages.<locals>.<listcomp>c S s g | ] }d |j v r|j �qS r< �r` �r� �xr: r: r; r? � s ri )�iterr� � py_modules� ext_package� ext_modules� rpartition)rO rD Znested_modulesrF �module�package�_r: r: r; r� � s � �r� c c sL � | j pg }dd� |D �E d H | js$| jpg }dd� |D �E d H d S d S )Nc s s � | ] }d |vr|V qdS r1 r: r= r: r: r; r� � r� z*_find_top_level_modules.<locals>.<genexpr>c s s � | ] }d |j vr|j V qdS r1 r@ rA r: r: r; r� � s � )rD rE rF )rO rD rF r: r: r; r � s � �r r� rQ c s � �fdd�t | �D �}t|�S )Nc s i | ] }|t t|� ����qS r: )�_absolute_rootr r �rT rQ r: r; r� � s ��z'_find_package_roots.<locals>.<dictcomp>)�sorted�_remove_nested)r� rT rQ � pkg_rootsr: rL r; r � s �r rU c C s4 t | �}|j}|�� rt|�� �S t|�� |j �S )z(Works for packages and top-level modules)r rp rh rf rl r` )rU Zpath_rp r: r: r; rK � s rK rO c c sv � | D ]5}d|vr q|� d�}tt|�d dd�D ] }d�|d|� �}tt|| d��}|�� r4|| vr7|V qqdS )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. ri r! r ���NrF )r2 �range�lenrV r r rh )rO r �parts�iZ partial_namerU r: r: r; r � s � ���r r� � Iterator[tuple[str, list[str]]]c c sB � | D ]}t ||d�}t|��� r t|d��� s ||gfV qd S )NrF z __init__.py)r r rh )r� rO r rU r: r: r; r � s � ��r c sP t | �� �}tt| �� ��D ]\�� t� �fdd�| �� D ��r%|��� q|S )Nc 3 s* � | ]\}}�|kot �� ||�V qd S rG )� _is_nested)r� �other� other_path�rU r r: r; r� � s � � �z!_remove_nested.<locals>.<genexpr>)r �copy�reversedr� r� �any�pop)rO r� r: rY r; rN � s � �rN r r: rp � parent_pathc C sH t �|�}| �|dd��d��d�}| �|�o#|t �t|g|�R � �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 rF r! ri )r �normpathr� �stripr2 � startswithr )r r: rp r^ Z norm_pkg_path�restr: r: r; rV s �rV �dir_c C s t j| dd� t�| � | S )zFCreate a directory ensured to be empty. Existing files may be removed.T)� ignore_errors)r �rmtreerR �makedirs)rc r: r: r; r� s r� c @ s& e Zd Zd dd�Zdd� Zdd� Zd S ) rm r2 rN c C s" || _ || _|| _|| _g | _d S rG )rP rQ rn � editable_namer� )rL rP rn rg rQ r: r: r; r� s z _NamespaceInstaller.__init__c C s t j�| j| j| j �S )zInstallation target.)rR rU rV rn rg Z nspkg_extrK r: r: r; �_get_nspkg_file% s z#_NamespaceInstaller._get_nspkg_filec C s t t| j��S )z1Where the modules/packages should be loaded from.)�reprrf rQ rK r: r: r; � _get_root) s z _NamespaceInstaller._get_rootNr� )r= r> r? r� rh rj r: r: r: r; rm s rm a from __future__ import annotations import sys from importlib.machinery import ModuleSpec, PathFinder 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: dict[str, str] = {mapping!r} NAMESPACES: dict[str, list[str]] = {namespaces!r} PATH_PLACEHOLDER = {name!r} + ".__path_hook__" class _EditableFinder: # MetaPathFinder @classmethod def find_spec(cls, fullname: str, path=None, target=None) -> ModuleSpec | None: # type: ignore # Top-level packages and modules (we know these exist in the FS) if fullname in MAPPING: pkg_path = MAPPING[fullname] return cls._find_spec(fullname, Path(pkg_path)) # Handle immediate children modules (required for namespaces to work) # To avoid problems with case sensitivity in the file system we delegate # to the importlib.machinery implementation. parent, _, child = fullname.rpartition(".") if parent and parent in MAPPING: return PathFinder.find_spec(fullname, path=[MAPPING[parent]]) # Other levels of nesting should be handled automatically by importlib # using the parent path. return None @classmethod def _find_spec(cls, fullname: str, candidate_path: Path) -> ModuleSpec | None: 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) return None class _EditableNamespaceFinder: # PathEntryFinder @classmethod def _path_hook(cls, path) -> type[_EditableNamespaceFinder]: if path == PATH_PLACEHOLDER: return cls raise ImportError @classmethod def _paths(cls, fullname: str) -> list[str]: paths = NAMESPACES[fullname] if not paths and fullname in MAPPING: paths = [MAPPING[fullname]] # Always add placeholder, for 2 reasons: # 1. __path__ cannot be empty for the spec to be considered namespace. # 2. In the case of nested namespaces, we need to force # import machinery to query _EditableNamespaceFinder again. return [*paths, PATH_PLACEHOLDER] @classmethod def find_spec(cls, fullname: str, target=None) -> ModuleSpec | None: # type: ignore 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) -> None: 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 r` r� r �dict[str, list[str]]c C s* t t|�� t�d�d��}tj| ||d�S )z_Create a string containing the code for the``MetaPathFinder`` and ``PathEntryFinder``. r )r3 �r` r� r )r rM r� �operator� itemgetter�_FINDER_TEMPLATE�formatrl r: r: r; r � s r c @ s e Zd ZdZdS )r. zCFile system does not seem to support either symlinks or hard links.N)r= r> r? r@ r: r: r: r; r. � s r. )r rf r2 r )r$ r r2 r% )r� r/ rT r0 rJ r r2 r% )rO r r2 r; )r� r/ rT r� rQ r r2 r0 )rU r r2 rf )rO r0 r2 r; )r� r� rO r0 r2 rU )rO r0 r2 r0 ) r rf r: rf rp rf r^ rf r2 r% )rc r+ r2 r+ )r` rf r� r� r rk r2 rf )br@ � __future__r r �loggingrm rR r� r� �collections.abcr r r � contextlibr �enumr �inspectr � itertoolsr r �pathlibr Ztempfiler �typesr �typingr r r r rF r r r r r r r r/ r r Z discoveryr rO r �warningsr r r" r~ r# r� r$ rd r% r} r& r r' r� Ztyping_extensionsr( Z_vendor.wheel.wheelfiler* r+ � getLoggerr= r� r- r r� rC r� r� r� r� r� r� r� r6 r� r r rK r r rN rV r� Z Installerrm ro r Z FileErrorr. r: r: r: r; �<module> sz ) ! N A ) Y
| ver. 1.4 |
Github
|
.
| PHP 8.2.30 | Generation time: 0 |
proxy
|
phpinfo
|
Settings