o LK&h<@sddlmZddlZddlZddlZddlZddlZddlmZm Z ddl m Z ddl m Z ddl mZddlmZdd lmZmZdd lmZdd lmZddlmmZddlZdd lmZd Z dddZ!GdddejZddZ"GdddZ#dS)) annotationsN)IterableIterator)partial)glob)Path)unique_everseen)StrPathStrPathT) Distribution)SetuptoolsDeprecationWarning) convert_path)z*.pyizpy.typedreturnNonecCst|t|jtjBdSN)oschmodstatst_modeS_IWRITE)targetrN/var/www/html/venv/lib/python3.10/site-packages/setuptools/command/build_py.py make_writablesrcseZdZUdZded<dZded<dZded <d d Z  dNdOfdd ZdPddZ dQd!d"Z d#d$Z d%d&Z d'd(Z d)d*ZdRdSfd-d. ZdTd0d1ZdUd3d4ZdUd5d6ZdPd7d8ZdPd9d:ZdVd?d@ZdPdAdBZdCdDZdEdFZdGdHZdIdJZedWdLdMZZS)Xbuild_pyaXEnhanced '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 distributionFbool editable_modeNzStrPath | Noneexisting_egg_info_dircCs>tj||jj|_|jjpi|_d|jvr|jd=dSdS)N data_files)origrfinalize_optionsr package_dataexclude_package_data__dict__selfrrrr",s    zbuild_py.finalize_optionsTinfiler outfiler preserve_modepreserve_timeslink str | Nonelevelobjectrtuple[StrPathT | str, bool]cs:|rtt|}tt|}t||||||Sr)strrresolvesuper copy_file)r'r)r*r+r,r-r/ __class__rrr53s   zbuild_py.copy_filercCsT|js|jr |jr dS|jr||jr|||tjj |dddS)z?Build modules, packages, and copy data files to build directoryNF)include_bytecode) py_modulespackagesr build_modulesbuild_packagesbuild_package_data byte_compiler!r get_outputsr&rrrrunDsz build_py.runattrr2cCs&|dkr ||_|jStj||S)zlazily compute data filesr )_get_data_filesr r!r __getattr__)r'rArrrrCTs zbuild_py.__getattr__cCs|tt|j|jp dS)z?Generate list of '(package,src_dir,build_dir,filenames)' tuplesr)analyze_manifestlistmap_get_pkg_data_filesr:r&rrrrB[szbuild_py._get_data_filescCs$|jditt|j|jpdS)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% setdefaultrErFrGr:r&rrrget_data_files_without_manifest`sz(build_py.get_data_files_without_manifestcsJ||tjj|jg|d}fdd||D}|||fS)N.csg|] }tj|qSr)rpathrelpath).0filesrc_dirrr rs z0build_py._get_pkg_data_files..)get_package_dirrrLjoin build_libsplitfind_data_files)r'package build_dir filenamesrrPrrGjs    zbuild_py._get_pkg_data_filescCsd|j|j||td}tttdd|}tj|}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_FILESrFrr itertoolschain from_iterablefilterrrLisfilerHgetexclude_data_files)r'rXrQpatternsglobs_expanded globs_matches glob_filesfilesrrrrWxs  zbuild_py.find_data_filesr8 list[str]cs"|jr t|St|S)1See :class:`setuptools.commands.build.SubCommand`)rrEget_output_mappingkeysr4r?)r'r8r6rrr?s zbuild_py.get_outputsdict[str, str]cCs(t||}tt|dddS)rlcSs|dS)Nrr)xrrrsz-build_py.get_output_mapping..)key)r_r` _get_package_data_output_mapping_get_module_mappingdictsorted)r'mappingrrrrms zbuild_py.get_output_mappingIterator[tuple[str, str]]ccs>|D]\}}}|d}||j||}||fVqdS)z5Iterate over all modules producing (dest, src) pairs.rKN)find_all_modulesrVget_module_outfilerU)r'rXmodule module_filefilenamerrrrts   zbuild_py._get_module_mappingccsJ|jD]\}}}}|D]}tj||}tj||}||fVq qdS)z6Iterate over package data producing (dest, src) pairs.N)r rrLrT)r'rXrQrYrZr}rsrcfilerrrrss z)build_py._get_package_data_output_mappingcCs@|D]\}}|tj||||\}}t|qdS)z$Copy data files into build directoryN)rsmkpathrrLdirnamer5r)r'rr~_outf_copiedrrrr=s  zbuild_py.build_package_datacCshi|_|jjs dSi}|jpdD] }||t||<q|jr8t|jdr8|j}t|d}|j dd }n| d| d}|j }|jj}t}|||D]_}tjt|\} } d} | } | r| | kr| |vr| } tj| \} } tj| | } | r| | kr| |vsl| |vr| | kr|| rqRn||| | }|r|||j|| g|qRdS)Nrz SOURCES.txtzutf-8)encodingegg_info)rHrinclude_package_datar:assert_relativerSrrexists read_text splitlines run_commandget_finalized_commandrfilelistrj_IncludePackageDataAbuse_filter_build_filesrrLrVrT is_moduleimportable_subpackagewarnrIappend)r'src_dirsrX egg_info_dirmanifestrjei_cmdcheckrLdfprevoldfdf importablerrrrDsL     zbuild_py.analyze_manifestrj Iterable[str]r Iterator[str]c#sn|d}||j|j|jf}dd|D}|D]}tj|tj|r1tfdd|Dr4|VqdS)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. buildcSsg|] }|rtj|qSr)rrLnormpath)rNprrrrRsz0build_py._filter_build_files..c3s|]}|vVqdSrr)rNr norm_pathrr sz/build_py._filter_build_files..N) rrU build_temp build_baserrLrisabsall)r'rjrr build_dirs norm_dirsrOrrrrs  "zbuild_py._filter_build_filescCsdSrrr&rrrget_data_filesszbuild_py.get_data_filescCsz|j|WStyYnwtj|||}||j|<|r#|jjs%|S|jjD]}||ks6||dr8nq)|St|d }| }Wdn1sOwYd|vrbt j d|d|S)z8Check namespace packages' __init__ for declare_namespacerKrbNsdeclare_namespacezNamespace package problem: z 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_checkedKeyErrorr!r check_packagernamespace_packages startswithopenread distutilserrorsDistutilsError)r'rX package_dirinit_pypkgrcontentsrrrrs,        zbuild_py.check_packagecCs"i|_tj|d|_d|_dS)NF)rr!rinitialize_optionsrrr&rrrr s  zbuild_py.initialize_optionscCs0tj||}|jjdurtj|jj|S|Sr)r!rrSrsrc_rootrrLrT)r'rXresrrrrSs zbuild_py.get_package_dircs\t||j||}fdd|D}tj|}t|fddD}tt|S)z6Filter filenames for package's data files in 'src_dir'c3s|] }t|VqdSr)fnmatchrbrNpattern)rjrrr!z.build_py.exclude_data_files..c3s|] }|vr|VqdSrr)rNfn)badrrr%r)rEr]r$r_r`rasetr)r'rXrQrjrf match_groupsmatcheskeepersr)rrjrres  zbuild_py.exclude_data_filesrcs0t||dg||g}fdd|DS)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. c3s"|] }tjt|VqdSr)rrLrTrrrPrrr6s  z2build_py._get_platform_patterns..)r_r`rd)specrXrQr[ raw_patternsrrPrr])s   zbuild_py._get_platform_patterns)TTNr()r)r r*r r+rr,rr-r.r/r0rr1rr)rAr2)T)r8rrrk)rro)rrx)rjrrr rr)r)__name__ __module__ __qualname____doc____annotations__rrr"r5r@rCrBrJrGrWr?rmrtrsr=rDrrrrrSre staticmethodr] __classcell__rrr6rrs>             ) rcCs6tj|s|Sddlm}td|}||)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. )rrLrdistutils.errorsrtextwrapdedentlstrip)rLrmsgrrrr=s    rc@s@eZdZdZGdddeZddZddZdd Zd d Z d S) rz>Inform users that package or module is included as 'data file'c@seZdZdZdZdS)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)rrr_SUMMARY_DETAILSrrrr_WarningUsrcCs t|_dSr)r_already_warnedr&rrr__init__s z!_IncludePackageDataAbuse.__init__cCs |do|dtd S)Nz.py)endswithlen isidentifier)r'rOrrrrs z"_IncludePackageDataAbuse.is_modulecCs6t|j}tttj|j}|rd|g|SdS)NrK) rparentrEr_ takewhiler2rpartsrT)r'rrOrrrrrrs z._IncludePackageDataAbuse.importable_subpackagecCs,||jvr|jj|d|j|dSdS)N)r)rremitadd)r'rrrrrs z_IncludePackageDataAbuse.warnN) rrrrr rrrrrrrrrrRs+ rr)$ __future__rrr_rrrcollections.abcrr functoolsrrpathlibrmore_itertoolsr_pathr r distr warningsr distutils.command.build_pycommandrr!rrdistutils.utilrr^rrrrrrrs0         !