+ h<cs^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/#returnZNoneZformat"@/usr/lib/python3.14/site-packages/setuptools/command/build_py.py __annotate__rs>>T>cs\P!V\P!V4P\P,4R#N)osZchmodstatZst_modeZS_IWRITE)target&r make_writablers'HHVRWWV_,,t}}<=rcs*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 s\PPV4VPPVnVPP ;'g/VnRVP 9dVP RR#R#) data_filesN)origrfinalize_optionsr package_dataexclude_package_data__dict__selfrrr$Zbuild_py.finalize_options,sa &&t, --::$($5$5$J$J$P$Pb! 4== ( l+ )rcs4V^8dQhRRRRRRRRRR R R R R /#)rinfileroutfiler preserve_moderpreserve_timeslinkz str | NonelevelZobjectrztuple[StrPathT | str, bool]rrrrrbuild_py.__annotate__3sP            % rc s<V'dE\\V4P44p\\V4P44p\SV`WW4WV4#r)strrZresolvesuper copy_file)r)r*r+r,r-r.r/ __class__s&&&&&&&rr3Zbuild_py.copy_file3sO f--/0F$w-//12Gw ]D  rcr rrrrrrr0DsSSTSrc s~VP'gVP'dVP'dR#VP'dVP4VP'd!VP 4VP 4VP \PPVRR74R#)z?Build modules, packages, and copy data files to build directoryNF)include_bytecode) Z py_modulespackagesr Z build_modulesZbuild_packagesbuild_package_dataZ byte_compiler#r get_outputsr(rrrunZ build_py.runDs{4===T5G5G5G  ???    ===    !  # # % $--33D53QRrcr )rattrr1rrrrrr0Ts555rc sVR8Xd"VP4VnVP#\PP W4#)zlazily compute data filesr")_get_data_filesr"r#r __getattr__)r)r:&&rr<Zbuild_py.__getattr__Ts9 < "224DO?? "}}((44rc sVP4\\VPVP;'gR44#)z?Generate list of '(package,src_dir,build_dir,filenames)' tuplesr)analyze_manifestlistmap_get_pkg_data_filesr6r(rrr;Zbuild_py._get_data_files[s2 C00$--2E2E2FGGrc sVPPR/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' setdefaultr?r@rAr6r(rrget_data_files_without_manifestZ(build_py.get_data_files_without_manifest`s=   !126C00$--2E2E2FGGrc s.VPV4p\PP!VP.VP R4,!pVP W4Uu.uF"p\PPWB4NK$ ppWW53#uupi).)get_package_dirrpathjoin build_libsplitfind_data_filesZrelpath)r)packagesrc_dir build_dirfile filenamess&& rrAZbuild_py._get_pkg_data_filesjs&&w/GGLLDNN#3gmmC6H#HJ ,,W> > GGOOD *>  55  s$(Bc sVPVPVV\R7p\\ \ RR7V4p\ PPV4p\\PPV4p\ P!VPPV.4V4pVPWV4#)z6Return filenames for package's data files in 'src_dir')extra_patternsT)Z recursive)_get_platform_patternsr%_IMPLICIT_DATA_FILESr@rr itertoolschain from_iterablefilterrrGZisfilerBgetexclude_data_files)r)rLrMpatternsZglobs_expandedZ globs_matchesZ glob_filesfiless&&& rrKZbuild_py.find_data_filesxs..     / /  WTT:HE!55nE BGGNNM:     # #GR 0  &&w??rcs V^8dQhRRRR/#)rr5rrz list[str]rrrrrr0s55D5I5rc s<VP'd(\VP4P44#\SV`V4#)1See :class:`setuptools.commands.build.SubCommand`)r r?get_output_mappingZkeysr2r8)r)r5r4s&&rr8Zbuild_py.get_outputss=    //16689 9w"#344rcr )rrzdict[str, str]rrrrrr0s99N9rc s\P!VP4VP44p\ \ VRR74#)r\csV^,#)rr)ZxrrZZ-build_py.get_output_mapping..s!A$r)Zkey)rTrU _get_package_data_output_mapping_get_module_mappingZdictZsorted)r)Zmappings& rr]Zbuild_py.get_output_mappings<//  1 1 3  $ $ & F7788rcr rrzIterator[tuple[str, str]]rrrrrr0s**%>*rc# s"VP4F8wrpVPR4pVPVPW4pWC3xK: R#5i)z5Iterate over all modules producing (dest, src) pairs.rEN)Zfind_all_modulesrJZget_module_outfilerI)r)rLZmoduleZ module_filefilename& rr_Zbuild_py._get_module_mappingsK,0,A,A,C (G[mmC(G..t~~wOH) )-DsAAcr r`rrrrrr0s((2K(rc# s"VPFRwrr4VFFp\PPW54p\PPW%4pWg3xKH KT R#5i)z6Iterate over package data producing (dest, src) pairs.N)r"rrGrH)r)rLrMrNrPrarsrcfiles& rr^Z)build_py._get_package_data_output_mappingsP6:oo 2Gi%i:'',,w9''&7FsA%A'cr rrrrrrr0s""D"rc sVP4FQwrVP\PP V44VP W!4wr4\ V4KS R#)z$Copy data files into build directoryN)r^ZmkpathrrGZdirnamer3r)r)rrcZ_outfZ_copiedrbrr7Zbuild_py.build_package_datasI#DDFOF KK/ 0!^^GZbuild_py.analyze_manifests46  555 #%}}***GGN_T%9%9'%BC D+  & & &T//?FFHH55LL-8H&&&8CCEE   Z (// ;F!??LOO))E(*,,UAD77==!67DADD a&7 a(GGLL'}9q)) *"'!Z/build_py._filter_build_files..s-T)Qy.@)sFTN) rfrIZ build_tempZ build_baserrGZnormpathisabsZall) r)r[rdroZ build_dirsZpZ norm_dirsrOrqs &&& @rrhZbuild_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 cr rrrrrrr0s   rc sR#rrr(rrget_data_filesZbuild_py.get_data_filess rc sXVPV,# \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_namespacerEZrbNsdeclare_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_checkedZKeyErrorr#r check_packagerZnamespace_packagesZ startswithZopenZread distutilsZerrorsZDistutilsError)r)rLZ package_dirZinit_pypkgrmZcontentss&&& rrwZbuild_py.check_packages ((1 1   ----d[I)0g&d//BBBN$$77C~# !>!>8N '4 AvvxH! x /""11-gY788  s ##C-- C= c sn/Vn\PPV4RVnRVnR#)FN)rvr#rinitialize_optionsr r!r(rrrzZbuild_py.initialize_options s, " ((."%)"rc s\PPW4pVPPe5\ P PVPPV4#V#r)r#rrFrZsrc_rootrrGrH)r)rLZress&& rrFZbuild_py.get_package_dirsNmm++D:    % % 177<< 1 1 : :C@ @ rc saa\S4oVPVPVV4pV3RlV4p\PP V4p\ V4oV3RlS4p\\V44#)z6Filter filenames for package's data files in 'src_dir'c3sR<"TFp\P!SV4xK R#5ir)fnmatchrW)rppatternr[rrrrs.build_py.exclude_data_files..!sOh7ug66hs$'c3s8<"TFqS9gK VxK R#5irr)rpZfnbadrrrrsr}%s7"322s )r?rRr&rTrUrVsetr) r)rLrMr[rZZ match_groupsZmatchesZkeepersr~s &&&f @rrYZbuild_py.exclude_data_filessoU ..  % %    PhO //// ='l77OG,--rc sa\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. Zc3sv<"TF.p\PPS\V44xK0 R#5ir)rrGrHr )rpr|rMrrrrsZ2build_py._get_platform_patterns..6s1 ( GGLL,w"7 8 8's69)rTrUrX)ZspecrLrMrQZ raw_patternss&&f& rrRZbuild_py._get_platform_patterns)sF!  HHR  HHWb !  (  r)r"r r&r!rBr%rv)TTNi)T)r) __name__ __module__ __qualname____firstlineno____doc__Z__annotations__r r!r$r3r9r<r;rDrArKr8r]r_r^r7r>rhrurwrzrFrYZ staticmethodrR__static_attributes__Z __classcell__)r4s@rrrsM4,0>0,  "S 5H H 6@$55 9*("'MR* <*  .   rrcs\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. )rrGrtdistutils.errorsrtextwrapZdedentZlstrip)rGrZmsgs& rrere=sS 77==   4    &(   c ""rcsH]tRtRtRt!RR]4tRtRtRt Rt R t R #) rgiRz>Inform users that package or module is included as 'data file'cs]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)rrrrZ_SUMMARYZ_DETAILSrrrr_WarningrUs " rrc s$\4VnR#r)r_already_warnedr(rr__init__Z!_IncludePackageDataAbuse.__init__s "urc snVPR4;'dVR\R4)P4#)z.pyN)ZendswithZlen isidentifier)r)rOr=rriZ"_IncludePackageDataAbuse.is_modules/}}U#JJ]E {(;(H(H(JJrc s\V4Pp\\P!\ P VP44pV'dRPV.VO4#R#)rEN) rparentr?rTZ takewhiler1rpartsrH)r)rrOryrs&&& rrjZ._IncludePackageDataAbuse.importable_subpackagesO4jY(()9)9399EF 88V,e,- -rc sWP9d:VPPVR7VPPV4R#R#))rnN)rrZemitZadd)r)rnr=rrkZ_IncludePackageDataAbuse.warns< 11 1 MM  *  5  $ $Z 0 2r)rN) rrrrrr rrrirjrkrrrrrgrgRs(H' /' V%K1rrg)z*.pyizpy.typed)$Z __future__rr{rTrrrZcollections.abcrrZ functoolsrrZpathlibrZmore_itertoolsrZ_pathrr Zdistr Zwarningsr Zdistutils.command.build_pyZcommandrr#rrxZdistutils.utilr rSrrergrrrrsh" .*%3))',>\ t}}\ ~#*>1>1r