U aʹj<@sddlmZddlZddlZddlZddlZddlZddlmZddl m Z ddl m Z ddl m Z mZddlmZddlmZd d lmZd d lmZddlmmZddlZdd lmZd ZddZ GdddejZddZ!GdddZ"dS)) annotationsN)partial)glob)Path)IterableIterator)unique_everseen)StrPath) Distribution)SetuptoolsDeprecationWarning) convert_path)z*.pyizpy.typedcCst|t|jtjBdSN)oschmodstatst_modeS_IWRITE)targetrZ/var/www/html/bwave/python/venv/lib/python3.8/site-packages/setuptools/command/build_py.py make_writablesrcs2eZdZUdZded<dZded<dZded <d d ZdFdddddddfdd ZddZ ddddZ ddZ ddZ ddZ dd Zd!d"ZdGdd#d$fd%d& Zd'd(d)d*Zd+d(d,d-Zd+d(d.d/Zd0d1Zd2d3Zd4dd5d6d7d8Zd9d:Zd;d<Zd=d>Zd?d@ZdAdBZedHdDdEZZS)Ibuild_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_modeNz str | Noneexisting_egg_info_dircCs@tj||jj|_|jjp i|_d|jkr6|jd=g|_dS)N data_files)origrfinalize_optionsr package_dataexclude_package_data__dict___build_py__updated_filesselfrrrr-s    zbuild_py.finalize_optionsTr object)infileoutfile preserve_modepreserve_timeslinklevelcs:|r$tt|}tt|}t||||||Sr)strrresolvesuper copy_file)r%r(r)r*r+r,r- __class__rrr15s zbuild_py.copy_filecCsT|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_compilerr get_outputsr$rrrrunFsz build_py.runr.)attrcCs&|dkr||_|jStj||S)zlazily compute data filesr)_get_data_filesrrr __getattr__)r%r;rrrr=Vs zbuild_py.__getattr__cCs.tj||||\}}|r&|j|||fSr)rr build_moduler#append)r%module module_filepackager)copiedrrrr>]s zbuild_py.build_modulecCs|tt|j|jpdS)z?Generate list of '(package,src_dir,build_dir,filenames)' tuplesr)analyze_manifestlistmap_get_pkg_data_filesr6r$rrrr<cszbuild_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" setdefaultrErFrGr6r$rrrget_data_files_without_manifesthsz(build_py.get_data_files_without_manifestcsJ||tjj|jg|d}fdd||D}|||fS)N.csg|]}tj|qSr)rpathrelpath).0filesrc_dirrr zsz0build_py._get_pkg_data_files..)get_package_dirrrLjoin build_libsplitfind_data_files)r%rB build_dir filenamesrrPrrGrs    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%rBrQpatternsZglobs_expandedZ globs_matchesZ glob_filesfilesrrrrWs  zbuild_py.find_data_filesz list[str])r4returncs"|jrt|St|S)1See :class:`setuptools.commands.build.SubCommand`)rrEget_output_mappingkeysr0r9)r%r4r2rrr9szbuild_py.get_outputszdict[str, str])rgcCs(t||}tt|dddS)rhcSs|dS)Nrr)xrrrz-build_py.get_output_mapping..)key)r^r_ _get_package_data_output_mapping_get_module_mappingdictsorted)r%mappingrrrris zbuild_py.get_output_mappingzIterator[tuple[str, str]]ccs<|D].\}}}|d}||j||}||fVqdS)z5Iterate over all modules producing (dest, src) pairs.rKN)Zfind_all_modulesrVZget_module_outfilerU)r%rBr@rAfilenamerrrrps zbuild_py._get_module_mappingccsH|jD]<\}}}}|D]*}tj||}tj||}||fVqqdS)z6Iterate over package data producing (dest, src) pairs.N)rrrLrT)r%rBrQrXrYrtrsrcfilerrrros z)build_py._get_package_data_output_mappingcCs@|D]2\}}|tj||||\}}t|qdS)z$Copy data files into build directoryN)romkpathrrLdirnamer1r)r%rruZ_outfZ_copiedrrrr7szbuild_py.build_package_datacCsji|_}|jjsdSi}|jp"dD]}||t||<q$t|ddrzt|jd rz|j}t|d}|j dd }n"| d| d}|j}|jj}t}|||D]} tjt| \} } d} | } | r | | kr | |kr | } tj| \} }tj|| } q| |kr| | kr.|| rNqn ||| | }|rN||||| g| qdS)Nrrz SOURCES.txtzutf-8)encodingegg_info)rHrZinclude_package_datar6assert_relativerSgetattrrrexists read_text splitlines run_commandget_finalized_commandryfilelistrf_IncludePackageDataAbuse_filter_build_filesrrLrVrT is_moduleimportable_subpackagewarnrIr?)r%mfZsrc_dirsrB egg_info_dirmanifestrfZei_cmdcheckrLdfprevZoldfZdf importablerrrrDsD        zbuild_py.analyze_manifestz Iterable[str]z Iterator[str])rfryrgc#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)rrLnormpath)rNprrrrRsz0build_py._filter_build_files..c3s|]}|kVqdSrr)rNrZ norm_pathrr sz/build_py._filter_build_files..N) rrU build_temp build_baserrLrisabsall)r%rfryrZ build_dirsZ norm_dirsrOrrrrs  "zbuild_py._filter_build_filescCsdSrrr$rrrget_data_filesszbuild_py.get_data_filesc Csz |j|WStk r YnXtj|||}||j|<|rH|jjsL|S|jjD]}||ksn||drTqxqT|St|d}| }W5QRXd|krt j d|f|S)z8Check namespace packages' __init__ for declare_namespacerKrbsdeclare_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_checkedKeyErrorrr check_packagernamespace_packages startswithopenread distutilserrorsDistutilsError)r%rB package_dirZinit_pypkgrcontentsrrrrs*     zbuild_py.check_packagecCs"i|_tj|d|_d|_dS)NF)rrrinitialize_optionsrrr$rrrrs zbuild_py.initialize_optionscCs0tj||}|jjdk r,tj|jj|S|Sr)rrrSrZsrc_rootrrLrT)r%rBresrrrrSs 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)fnmatchrarNpattern)rfrrr'sz.build_py.exclude_data_files..c3s|]}|kr|VqdSrr)rNfn)badrrr+s)rEr\r!r^r_r`setr)r%rBrQrfreZ match_groupsmatchesZkeepersr)rrfrrds 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)rrLrTr rrPrrr<sz2build_py._get_platform_patterns..)r^r_rc)specrBrQrZZ raw_patternsrrPrr\/s   zbuild_py._get_platform_patterns)TTNr&)T)r)__name__ __module__ __qualname____doc____annotations__rrrr1r:r=r>r<rJrGrWr9rirpror7rDrrrrrSrd staticmethodr\ __classcell__rrr2rrs>      )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. )rrLrdistutils.errorsrtextwrapdedentlstrip)rLrmsgrrrrzCs    rzc@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_Warning[srcCs t|_dSr)r_already_warnedr$rrr__init__sz!_IncludePackageDataAbuse.__init__cCs |do|dtd S)Nz.py)endswithlen isidentifier)r%rOrrrrsz"_IncludePackageDataAbuse.is_modulecCs6t|j}tttj|j}|r2d|f|SdS)NrK) rparentrEr^ takewhiler.rpartsrT)r%rrOrrrrrrs  z._IncludePackageDataAbuse.importable_subpackagecCs(||jkr$|jj|d|j|dS)N)r)rremitadd)r%rrrrrs z_IncludePackageDataAbuse.warnN) rrrrr rrrrrrrrrrXs +r)# __future__rrr^rrr functoolsrrpathlibrtypingrrZmore_itertoolsrZsetuptools._pathr distr warningsr Zdistutils.command.build_pycommandrrrrdistutils.utilr r]rrzrrrrrs.         &