+ h<^RIHt^RIt^RIt^RIt^RIt^RIt^RIHtH t ^RI H t ^RI H t ^RI Ht^RIHt^RIHtHt^R IHt^R IHt^RIHuHt^RIt^R IHtRt R R lt!!RR]P44tRt"!RR4t#R#)) annotationsN)IterableIterator)partial)glob)Path)unique_everseen)StrPathStrPathT) Distribution)SetuptoolsDeprecationWarning) convert_pathcV^8dQhRR/#returnNone)formats"=/usr/lib/python3/dist-packages/setuptools/command/build_py.py __annotate__rs>>T>c\P!V\P!V4P\P,4R#N)oschmodstatst_modeS_IWRITE)targets&r make_writabler!s'HHVRWWV_,,t}}<=rc*a]tRt^t$RtR]R&RtR]R&RtR]R &R tR+R V3R lllt R Rlt RRlt Rt Rt RtRtR,RV3RllltRRltRRltRRltRRltRR ltR!R"ltR#R$ltR%tR&tR'tR(t]R-R)l4tR*tV;t#).build_pyaDEnhanced '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_dirc \PPV4VPPVnVPP ;'g/VnRVP 9dVP RR#R#) data_filesN)origr#finalize_optionsr$ package_dataexclude_package_data__dict__selfs&rr+build_py.finalize_options,sa &&t, --::$($5$5$J$J$P$Pb! 4== ( l+ )rc4V^8dQhRRRRRRRRRR R R R R /#)rinfiler outfiler preserve_moder%preserve_timeslinkz str | Nonelevelobjectrztuple[StrPathT | str, bool]r)rs"rrbuild_py.__annotate__3sP            % rc <V'dE\\V4P44p\\V4P44p\SV`WW4WV4#r)strrresolvesuper copy_file)r0r3r4r5r6r7r8 __class__s&&&&&&&rr?build_py.copy_file3sO f--/0F$w-//12Gw ]D  rcV^8dQhRR/#rr)rs"rrr:DsSSTSrc ~VP'gVP'dVP'dR#VP'dVP4VP'd!VP 4VP 4VP \PPVRR74R#)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/s&rrun build_py.runDs{4===T5G5G5G  ???    ===    !  # # % $--33D53QRrcV^8dQhRR/#)rattrr<r)rs"rrr:Ts555rc VR8Xd"VP4VnVP#\PP W4#)zlazily compute data filesr))_get_data_filesr)r*r# __getattr__)r0rOs&&rrRbuild_py.__getattr__Ts9 < "224DO?? "}}((44rc VP4\\VPVP;'gR44#)z?Generate list of '(package,src_dir,build_dir,filenames)' tuplesr)analyze_manifestlistmap_get_pkg_data_filesrFr/s&rrQbuild_py._get_data_files[s2 C00$--2E2E2FGGrc VPPR/4\\VPVP ;'gR44#)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. setdefaultrVrWrXrFr/s&rget_data_files_without_manifest(build_py.get_data_files_without_manifest`s=   !126C00$--2E2E2FGGrc .VPV4p\PP!VP.VP R4,!pVP W4Uu.uF"p\PPWB4NK$ ppWW53#uupi).)get_package_dirrpathjoin build_libsplitfind_data_filesrelpath)r0packagesrc_dir build_dirfile filenamess&& rrXbuild_py._get_pkg_data_filesjs&&w/GGLLDNN#3gmmC6H#HJ ,,W> > GGOOD *>  55  s$(Bc VPVPVV\R7p\\ \ RR7V4p\ PPV4p\\PPV4p\ P!VPPV.4V4pVPWV4#)z6Return filenames for package's data files in 'src_dir')extra_patternsT) recursive)_get_platform_patternsr,_IMPLICIT_DATA_FILESrWrr itertoolschain from_iterablefilterrrbisfiler[getexclude_data_files)r0rhripatternsglobs_expanded globs_matches glob_filesfiless&&& rrfbuild_py.find_data_filesxs..     / /  WTT:HE!55nE BGGNNM:     # #GR 0  &&w??rc V^8dQhRRRR/#)rrDr%rz list[str]r)rs"rrr:s55D5I5rc <VP'd(\VP4P44#\SV`V4#)1See :class:`setuptools.commands.build.SubCommand`)r&rVget_output_mappingkeysr>rK)r0rDr@s&&rrKbuild_py.get_outputss=    //16689 9w"#344rcV^8dQhRR/#)rrzdict[str, str]r)rs"rrr:s99N9rc \P!VP4VP44p\ \ VRR74#)rcV^,#)rr)xs&r-build_py.get_output_mapping..s!A$r)key)rsrt _get_package_data_output_mapping_get_module_mappingdictsorted)r0mappings& rrbuild_py.get_output_mappings<//  1 1 3  $ $ & F7788rcV^8dQhRR/#rrzIterator[tuple[str, str]]r)rs"rrr:s**%>*rc# "VP4F8wrpVPR4pVPVPW4pWC3xK: R#5i)z5Iterate over all modules producing (dest, src) pairs.r`N)find_all_modulesreget_module_outfilerd)r0rhmodule module_filefilenames& rrbuild_py._get_module_mappingsK,0,A,A,C (G[mmC(G..t~~wOH) )-DsAAcV^8dQhRR/#rr)rs"rrr:s((2K(rc# "VPFRwrr4VFFp\PPW54p\PPW%4pWg3xKH KT R#5i)z6Iterate over package data producing (dest, src) pairs.N)r)rrbrc)r0rhrirjrlrr srcfiles& rr)build_py._get_package_data_output_mappingsP6:oo 2Gi%i:'',,w9''&7FsA%A'cV^8dQhRR/#rr)rs"rrr:s""D"rc VP4FQwrVP\PP V44VP W!4wr4\ V4KS R#)z$Copy data files into build directoryN)rmkpathrrbdirnamer?r!)r0r r_outf_copieds& rrIbuild_py.build_package_datasI#DDFOF KK/ 0!^^G/build_py._filter_build_files..s-T)Qy.@)sFTN) rrd build_temp build_baserrbnormpathisabsall) r0r~rr build_dirsp norm_dirsrkrs &&& @rrbuild_py._filter_build_filess**730@0@%BRBRS 2<B*Q(RWW%%a(* BD((.I77==&&##-T)-T###-T)-T*T*T Cs)9D  D #D-AD D D :D cV^8dQhRR/#rr)rs"rrr:s   rc R#rrr/s&rget_data_filesbuild_py.get_data_filess rc XVPV,# \dMi;i\PP YT4pY0PT&T'dTP P 'gT#TP P F)pYA8Xg!TPTR,4'gK)M T#\TR4;_uu_4pTP4pRRR4M +'giM;iRX9d$\PPRT R24hT#)z8Check namespace packages' __init__ for declare_namespacer`rbNsdeclare_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_packager$namespace_packages startswithopenread distutilserrorsDistutilsError)r0rh package_dirinit_pypkgrcontentss&&& rrbuild_py.check_packages ((1 1   ----d[I)0g&d//BBBN$$77C~# !>!>8N '4 AvvxH! x /""11-gY788  s ##C-- C= c n/Vn\PPV4RVnRVnR#)FN)rr*r#initialize_optionsr&r'r/s&rrbuild_py.initialize_options s, " ((."%)"rc \PPW4pVPPe5\ P PVPPV4#V#r)r*r#rar$src_rootrrbrc)r0rhress&& rrabuild_py.get_package_dirsNmm++D:    % % 177<< 1 1 : :C@ @ rc aa\S4oVPVPVV4pV3RlV4p\PP V4p\ V4oV3RlS4p\\V44#)z6Filter filenames for package's data files in 'src_dir'c3R<"TFp\P!SV4xK R#5ir)fnmatchrv)rpatternr~s& rr.build_py.exclude_data_files..!sOh7ug66hs$'c38<"TFqS9gK VxK R#5irr)rfnbads& rrr%s7"322s )rVrqr-rsrtrusetr ) r0rhrir~rz match_groupsmatcheskeepersrs &&&f @rrybuild_py.exclude_data_filessoU ..  % %    PhO //// ='l77OG,--rc a\P!VVPR.4VPV.44pV3RlV4#)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. c3v<"TF.p\PPS\V44xK0 R#5ir)rrbrcr)rrris& rr2build_py._get_platform_patterns..6s1 ( GGLL,w"7 8 8's69)rsrtrx)specrhriro raw_patternss&&f& rrqbuild_py._get_platform_patterns)sF!  HHR  HHWb !  (  r)r)r&r-r'r[r,r)TTN)T)r) __name__ __module__ __qualname____firstlineno____doc____annotations__r&r'r+r?rLrRrQr]rXrfrKrrrrIrUrrrrrary staticmethodrq__static_attributes__ __classcell__)r@s@rr#r#sM4,0>0,  "S 5H H 6@$55 9*("'MR* <*  .   rr#c\PPV4'gV#^RIHp\ P !R4P4V,pV!V4h)r)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. )rrbrdistutils.errorsrtextwrapdedentlstrip)rbrmsgs& rrr=sS 77==   4    &(   c ""rcH]tRtRtRt!RR]4tRtRtRt Rt R t R #) riRz>Inform users that package or module is included as 'data file'c]tRtRtRtRtRtR#)!_IncludePackageDataAbuse._WarningiUzU 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. rN)rrr r _SUMMARY_DETAILSrrrr_WarningrUs " rrc $\4VnR#r)r_already_warnedr/s&r__init__!_IncludePackageDataAbuse.__init__s "urc nVPR4;'dVR\R4)P4#)z.pyN)endswithlen isidentifier)r0rks&&rr"_IncludePackageDataAbuse.is_modules/}}U#JJ]E {(;(H(H(JJrc \V4Pp\\P!\ P VP44pV'dRPV.VO4#R#)r`N) rparentrVrs takewhiler<r$partsrc)r0r'rkrr)s&&& rr._IncludePackageDataAbuse.importable_subpackagesO4jY(()9)9399EF 88V,e,- -rc WP9d:VPPVR7VPPV4R#R#))rN)rremitadd)r0rs&&rr_IncludePackageDataAbuse.warns< 11 1 MM  *  5  $ $Z 0 2r)rN) rrr r r r rrrrrrrrrrrRs(H' /' V%K1rr)z*.pyizpy.typed)$ __future__rrrsrrrcollections.abcrr functoolsrrpathlibrmore_itertoolsr _pathr r distr warningsr distutils.command.build_pycommandr#r*rrdistutils.utilrrrr!rrrrrr:sh" .*%3))',>\ t}}\ ~#*>1>1r