o
    g;                     @  s   d dl mZ d dlZd dlZd dlZd dlZd dlZd dlmZ d dl	m	Z	 d dl
mZ d dlmZmZ d dlmZ dd	lmZ dd
lmZ d dlm  mZ d dlZd dlmZ dZdd ZG dd dejZdd ZG dd dZ dS )    )annotationsN)partial)glob)Path)IterableIterator)unique_everseen   )Distribution)SetuptoolsDeprecationWarning)convert_path)z*.pyizpy.typedc                 C  s   t | t | jtjB  d S N)oschmodstatst_modeS_IWRITE)target r   X/var/www/rescue_company/venv/lib/python3.10/site-packages/setuptools/command/build_py.pymake_writable   s   r   c                      s  e Zd ZU dZded< dZded< dZded	< d
d Z				dC fdd	Zdd Z	dDddZ
dd Zdd Zdd Zdd Zdd ZdEdF fd"d#ZdGd%d&ZdHd(d)ZdHd*d+Zd,d- Zd.d/ ZdId4d5Zd6d7 Zd8d9 Zd:d; Zd<d= Zd>d? ZedJdAdBZ  ZS )K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.
    r
   distributionFbooleditable_modeNz
str | Noneexisting_egg_info_dirc                 C  s@   t j|  | jj| _| jjpi | _d| jv r| jd= g | _d S )N
data_files)origr   finalize_optionsr   package_dataexclude_package_data__dict___build_py__updated_filesselfr   r   r   r   +   s   


zbuild_py.finalize_optionsT   c                   s:   |rt t| }t t| }t ||||||S r   )strr   resolvesuper	copy_file)r$   infileoutfilepreserve_modepreserve_timeslinklevel	__class__r   r   r)   3   s   
zbuild_py.copy_filec                 C  sT   | j s| jr	| jrdS | j r|   | jr|   |   | tjj	| dd dS )z?Build modules, packages, and copy data files to build directoryNF)include_bytecode)

py_modulespackagesr   build_modulesbuild_packagesbuild_package_databyte_compiler   r   get_outputsr#   r   r   r   runD   s   zbuild_py.runattrr&   c                 C  s&   |dkr|   | _| jS tj| |S )zlazily compute data filesr   )_get_data_filesr   r   r   __getattr__)r$   r;   r   r   r   r=   T   s   
zbuild_py.__getattr__c                 C  s.   t j| |||\}}|r| j| ||fS r   )r   r   build_moduler"   append)r$   modulemodule_filepackager+   copiedr   r   r   r>   [   s   zbuild_py.build_modulec                 C  s   |    tt| j| jpdS )z?Generate list of '(package,src_dir,build_dir,filenames)' tuplesr   )analyze_manifestlistmap_get_pkg_data_filesr4   r#   r   r   r   r<   a   s   zbuild_py._get_data_filesc                 C  s$   | j di  tt| j| jp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!   
setdefaultrE   rF   rG   r4   r#   r   r   r   get_data_files_without_manifestf   s   z(build_py.get_data_files_without_manifestc                   sJ   |  | tjj| jg|d  } fdd| | D }| ||fS )N.c                   s   g | ]	}t j| qS r   )r   pathrelpath).0filesrc_dirr   r   
<listcomp>x   s    z0build_py._get_pkg_data_files.<locals>.<listcomp>)get_package_dirr   rL   join	build_libsplitfind_data_files)r$   rB   	build_dir	filenamesr   rP   r   rG   p   s   


zbuild_py._get_pkg_data_filesc                 C  sd   | j | j||td}tttdd|}tj|}t	t
jj|}t| j|g |}| |||S )z6Return filenames for package's data files in 'src_dir')extra_patternsT)	recursive)_get_platform_patternsr   _IMPLICIT_DATA_FILESrF   r   r   	itertoolschainfrom_iterablefilterr   rL   isfilerH   getexclude_data_files)r$   rB   rQ   patternsglobs_expandedglobs_matches
glob_filesfilesr   r   r   rW   ~   s   zbuild_py.find_data_filesreturn	list[str]c                   s"   | j rt|   S t |S )1See :class:`setuptools.commands.build.SubCommand`)r   rE   get_output_mappingkeysr(   r9   )r$   r2   r0   r   r   r9      s   zbuild_py.get_outputsdict[str, str]c                 C  s(   t |  |  }tt|dd dS )rl   c                 S  s   | d S )Nr   r   )xr   r   r   <lambda>   s    z-build_py.get_output_mapping.<locals>.<lambda>)key)r^   r_    _get_package_data_output_mapping_get_module_mappingdictsorted)r$   mappingr   r   r   rm      s
   zbuild_py.get_output_mappingIterator[tuple[str, str]]c                 c  s>    |   D ]\}}}|d}| | j||}||fV  qdS )z5Iterate over all modules producing (dest, src) pairs.rK   N)find_all_modulesrV   get_module_outfilerU   )r$   rB   r@   rA   filenamer   r   r   rt      s   
zbuild_py._get_module_mappingc                 c  sJ    | j D ]\}}}}|D ]}tj||}tj||}||fV  qqdS )z6Iterate over package data producing (dest, src) pairs.N)r   r   rL   rT   )r$   rB   rQ   rX   rY   r{   r   srcfiler   r   r   rs      s   z)build_py._get_package_data_output_mappingc                 C  s@   |   D ]\}}| tj| | ||\}}t| qdS )z$Copy data files into build directoryN)rs   mkpathr   rL   dirnamer)   r   )r$   r   r|   _outf_copiedr   r   r   r7      s
   
zbuild_py.build_package_datac                 C  sp  i  | _ }| jjsd S i }| jpdD ]}||t| |< qt| dd r=t| jd	 r=| j}t|d}|j
dd }n| d | d}|j}|jj}t }| ||D ]^}	tjt|	\}
}d }|}|
r|
|kr|
|vr|
}tj|
\}
}tj||}|
r|
|kr|
|vsq|
|v r||kr||rqWn|||
 |}|r|| |||
 g |	 qWd S )Nr   r   zSOURCES.txtzutf-8)encodingegg_info)rH   r   include_package_datar4   assert_relativerS   getattrr   r   exists	read_text
splitlinesrun_commandget_finalized_commandr   filelistri   _IncludePackageDataAbuse_filter_build_filesr   rL   rV   rT   	is_moduleimportable_subpackagewarnrI   r?   )r$   mfsrc_dirsrB   egg_info_dirmanifestri   ei_cmdcheckrL   dfprevoldfdf
importabler   r   r   rD      sL   






zbuild_py.analyze_manifestri   Iterable[str]r   Iterator[str]c                 #  sn    |  d}|| j|j|jf}dd |D }|D ]}tj| tj|r1t fdd|D r4|V  qdS )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 | ]
}|rt j|qS r   )r   rL   normpath)rN   pr   r   r   rR      s    z0build_py._filter_build_files.<locals>.<listcomp>c                 3  s    | ]}| vV  qd S r   r   )rN   r   	norm_pathr   r   	<genexpr>   s    z/build_py._filter_build_files.<locals>.<genexpr>N)	r   rU   
build_temp
build_baser   rL   r   isabsall)r$   ri   r   r   
build_dirs	norm_dirsrO   r   r   r   r      s   

"zbuild_py._filter_build_filesc                 C  s   d S r   r   r#   r   r   r   get_data_files   s   zbuild_py.get_data_filesc                 C  s   z| j | W S  ty   Y nw tj| ||}|| j |< |r#| jjs%|S | jjD ]}||ks6||d r8 nq)|S t|d}|	 }W d   n1 sOw   Y  d|vrat
jd|f |S )z8Check namespace packages' __init__ for declare_namespacerK   rbNs   declare_namespacezNamespace 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   namespace_packages
startswithopenread	distutilserrorsDistutilsError)r$   rB   package_dirinit_pypkgr   contentsr   r   r   r      s0   

zbuild_py.check_packagec                 C  s"   i | _ tj|  d| _d | _d S )NF)r   r   r   initialize_optionsr   r   r#   r   r   r   r     s   
zbuild_py.initialize_optionsc                 C  s0   t j| |}| jjd urtj| jj|S |S r   )r   r   rS   r   src_rootr   rL   rT   )r$   rB   resr   r   r   rS     s   zbuild_py.get_package_dirc                   s\   t | | j||}fdd|D }tj|}t|  fddD }t t|S )z6Filter filenames for package's data files in 'src_dir'c                 3  s    | ]	}t  |V  qd S r   )fnmatchra   rN   pattern)ri   r   r   r   %      z.build_py.exclude_data_files.<locals>.<genexpr>c                 3  s    | ]	}| vr|V  qd S r   r   )rN   fn)badr   r   r   )  r   )rE   r\   r    r^   r_   r`   setr   )r$   rB   rQ   ri   re   match_groupsmatcheskeepersr   )r   ri   r   rd     s   zbuild_py.exclude_data_filesr   c                   s0   t || dg | |g } fdd|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  qd S r   )r   rL   rT   r   r   rP   r   r   r   :  s
    
z2build_py._get_platform_patterns.<locals>.<genexpr>)r^   r_   rc   )specrB   rQ   rZ   raw_patternsr   rP   r   r\   -  s   


zbuild_py._get_platform_patterns)TTNr%   )r;   r&   )T)rj   rk   )rj   ro   )rj   rx   )ri   r   r   r&   rj   r   )r   )__name__
__module____qualname____doc____annotations__r   r   r   r)   r:   r=   r>   r<   rJ   rG   rW   r9   rm   rt   rs   r7   rD   r   r   r   r   rS   rd   staticmethodr\   __classcell__r   r   r0   r   r      s@   
 	





)r   c                 C  s6   t j| s| S ddlm} td |  }||)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   rL   r   distutils.errorsr   textwrapdedentlstrip)rL   r   msgr   r   r   r   A  s   	r   c                   @  s@   e Zd ZdZG dd deZdd Zdd Zdd	 Zd
d Z	dS )r   z>Inform users that package or module is included as 'data file'c                   @  s   e Zd ZdZdZdS )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   _SUMMARY_DETAILSr   r   r   r   _WarningY  s    r   c                 C  s   t  | _d S r   )r   _already_warnedr#   r   r   r   __init__  s   z!_IncludePackageDataAbuse.__init__c                 C  s    | do|d td   S )Nz.py)endswithlenisidentifier)r$   rO   r   r   r   r     s    z"_IncludePackageDataAbuse.is_modulec                 C  s6   t |j}tttj|j}|rd|g|S d S )NrK   )	r   parentrE   r^   	takewhiler&   r   partsrT   )r$   r   rO   r   r   r   r   r   r     s
   
z._IncludePackageDataAbuse.importable_subpackagec                 C  s,   || j vr| jj|d | j | d S 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   r   V  s    +r   )!
__future__r   r   r^   r   r   r   	functoolsr   r   pathlibr   typingr   r   more_itertoolsr   distr
   warningsr   distutils.command.build_pycommandr   r   r   r   distutils.utilr   r]   r   r   r   r   r   r   r   <module>   s.      &