a 6Rh<@sddlmZddlZddlZddlZddlZddlZddlmZm Z ddl m Z ddl m Z ddl mZddlmZdd lmZmZdd lmZdd lmZddlmmZddlZdd lmZd Z ddddZ!GdddejZddZ"GdddZ#dS)) annotationsN)IterableIterator)partial)glob)Path)unique_everseen)StrPathStrPathT) Distribution)SetuptoolsDeprecationWarning) convert_path)z*.pyizpy.typedNonereturncCst|t|jtjBdSN)oschmodstatst_modeS_IWRITE)targetrQ/opt/python-3.9.24/usr/lib/python3.9/site-packages/setuptools/command/build_py.py make_writablesrc sDeZdZUdZded<dZded<dZded <d d ZdHddddddddfdd ZddddZ ddddZ ddZ d d!Z d"d#Z d$d%ZdIdd&d'fd(d) Zd*dd+d,Zd-dd.d/Zd-dd0d1Zddd2d3Zddd4d5Zd6dd7d8d9d:Zddd;d<Zd=d>Zd?d@ZdAdBZdCdDZedJdFdGZZS)Kbuild_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|_|jjp i|_d|jvr6|jd=dS)N data_files)origrfinalize_optionsr package_dataexclude_package_data__dict__selfrrrr#,s    zbuild_py.finalize_optionsTr r z str | Noneobjectztuple[StrPathT | str, bool])infileoutfile preserve_modepreserve_timeslinklevelrcs:|r$tt|}tt|}t||||||Sr)strrresolvesuper copy_file)r(r+r,r-r.r/r0 __class__rrr43s  zbuild_py.copy_filerrcCsT|js |jr|jrdS|jr$||jr:|||tjj |dddS)z?Build modules, packages, and copy data files to build directoryNF)include_bytecode) py_modulespackagesrZ build_modulesZbuild_packagesbuild_package_data byte_compiler"r get_outputsr'rrrrunDsz build_py.runr1)attrcCs&|dkr||_|jStj||S)zlazily compute data filesr!)_get_data_filesr!r"r __getattr__)r(r>rrrr@Ts zbuild_py.__getattr__cCs|tt|j|jpdS)z?Generate list of '(package,src_dir,build_dir,filenames)' tuplesr)analyze_manifestlistmap_get_pkg_data_filesr9r'rrrr?[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& setdefaultrBrCrDr9r'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 rsz0build_py._get_pkg_data_files..)get_package_dirrrIjoin build_libsplitfind_data_files)r(package build_dir filenamesrrMrrDjs    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_FILESrCrr itertoolschain from_iterablefilterrrIisfilerEgetexclude_data_files)r(rUrNpatternsZglobs_expandedZ globs_matchesZ glob_filesfilesrrrrTxs  zbuild_py.find_data_filesz list[str])r7rcs"|jrt|St|S)1See :class:`setuptools.commands.build.SubCommand`)rrBget_output_mappingkeysr3r<)r(r7r5rrr<szbuild_py.get_outputszdict[str, str]cCs(t||}tt|dddS)recSs|dS)Nrr)xrrrz-build_py.get_output_mapping..)key)r\r] _get_package_data_output_mapping_get_module_mappingdictsorted)r(mappingrrrrfs zbuild_py.get_output_mappingzIterator[tuple[str, str]]ccs<|D].\}}}|d}||j||}||fVqdS)z5Iterate over all modules producing (dest, src) pairs.rHN)Zfind_all_modulesrSZget_module_outfilerR)r(rUmoduleZ module_filefilenamerrrrms zbuild_py._get_module_mappingccsH|jD]<\}}}}|D]*}tj||}tj||}||fVqqdS)z6Iterate over package data producing (dest, src) pairs.N)r!rrIrQ)r(rUrNrVrWrrrsrcfilerrrrls z)build_py._get_package_data_output_mappingcCs@|D]2\}}|tj||||\}}t|qdS)z$Copy data files into build directoryN)rlmkpathrrIdirnamer4r)r(rrsZ_outfZ_copiedrrrr:szbuild_py.build_package_datacCs\i|_|jjsdSi}|jpdD]}||t||<q |jrpt|jdrp|j}t|d}|j dd }n"| d| d}|j }|jj}t}|||D]}tjt|\} } d} | } | r| | kr| |vr| } tj| \} } tj| | } q| |vr| | kr|| r>qn ||| | }|r>|||j|| g|qdS)Nrz SOURCES.txtzutf-8)encodingegg_info)rErZinclude_package_datar9assert_relativerPr rexists read_text splitlines run_commandget_finalized_commandrwfilelistrd_IncludePackageDataAbuse_filter_build_filesrrIrSrQ is_moduleimportable_subpackagewarnrFappend)r(Zsrc_dirsrU egg_info_dirmanifestrdZei_cmdcheckrIdfprevZoldfZdf importablerrrrAsD      zbuild_py.analyze_manifestz Iterable[str]z Iterator[str])rdrwrc#sl|d}||j|j|jf}dd|D}|D]8}tj|tj|r`tfdd|Dr.|Vq.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. buildcSsg|]}|rtj|qSr)rrInormpath)rKprrrrOrjz0build_py._filter_build_files..c3s|]}|vVqdSrr)rKrZ norm_pathrr rjz/build_py._filter_build_files..N) r}rR build_temp build_baserrIrisabsall)r(rdrwrZ build_dirsZ norm_dirsrLrrrrs  "zbuild_py._filter_build_filescCsdSrrr'rrrget_data_filesszbuild_py.get_data_filescCsz |j|WStyYn0tj|||}||j|<|rF|jjsJ|S|jjD]}||ksl||drRqvqR|St|d}| }Wdn1s0Yd|vrt j d|d|S)z8Check namespace packages' __init__ for declare_namespacerHrbNsdeclare_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(rU package_dirZinit_pypkgrcontentsrrrrs&      & zbuild_py.check_packagecCs"i|_tj|d|_d|_dS)NF)rr"rinitialize_optionsrr r'rrrr s zbuild_py.initialize_optionscCs0tj||}|jjdur,tj|jj|S|Sr)r"rrPrZsrc_rootrrIrQ)r(rUresrrrrPs 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)fnmatchr_rKpattern)rdrrr!rjz.build_py.exclude_data_files..c3s|]}|vr|VqdSrr)rKfn)badrrr%rj)rBrZr%r\r]r^setr)r(rUrNrdrcZ match_groupsmatchesZkeepersr)rrdrrbs 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)rrIrQrrrMrrr6sz2build_py._get_platform_patterns..)r\r]ra)specrUrNrXZ raw_patternsrrMrrZ)s   zbuild_py._get_platform_patterns)TTNr))T)r)__name__ __module__ __qualname____doc____annotations__rr r#r4r=r@r?rGrDrTr<rfrmrlr:rArrrrrPrb staticmethodrZ __classcell__rrr5rrs<       )rcCs:tj|s|Sddlm}td|}||dS)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. )rrIrdistutils.errorsrtextwrapdedentlstrip)rIrmsgrrrrx=s    rxc@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)rrrZ_SUMMARYZ_DETAILSrrrr_WarningUsrcCs t|_dSr)r_already_warnedr'rrr__init__sz!_IncludePackageDataAbuse.__init__cCs |do|dtd S)Nz.py)endswithlen isidentifier)r(rLrrrrsz"_IncludePackageDataAbuse.is_modulecCs6t|j}tttj|j}|r2d|g|SdS)NrH) rparentrBr\ takewhiler1rpartsrQ)r(rrLrrrrrrs  z._IncludePackageDataAbuse.importable_subpackagecCs(||jvr$|jj|d|j|dS)N)r)rremitadd)r(rrrrrs z_IncludePackageDataAbuse.warnN) rrrrr rrrrrrrrrrRs +r)$ __future__rrr\rrrcollections.abcrr functoolsrrpathlibrZmore_itertoolsr_pathr r distr warningsr Zdistutils.command.build_pycommandrr"rrdistutils.utilrr[rrxrrrrrs.        !