JFIFxxC      C  " }!1AQa"q2#BR$3br %&'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz w!1AQaq"2B #3RbrJFIFxxC      C  " }!1AQa"q2#BR$3br %&'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz w!1AQaq"2B #3Rbr a0biH8SrSSKrSSKrSSKrSSKrSSKrSSKrSSKrSSKrSSK r SSK J r SSK J r JrJrJrJr SSKrSSKrSSKJr SSKJr SSKJr SS K Jr SS KJr /S Qr\R<"S S 5R?5r S\ RCSS5;r""SS\#5r$"SS\RJRL5r&\RNS5r(Sr)Sr*Sr+\RNS5r,\\ \-\\-\\-S44r."SS5r/"SS\/5r0"SS\05r1\0"5r2\2Rfr3\2Rhr4\2Rjr5\2Rlr6\2Rnr7\"(d$\2Rpr8\2Rrr9\2Rtr:\1"5r;g) a-A PEP 517 interface to setuptools Previously, when a user or a command line tool (let's call it a "frontend") needed to make a request of setuptools to take a certain action, for example, generating a list of installation requirements, the frontend would would call "setup.py egg_info" or "setup.py bdist_wheel" on the command line. PEP 517 defines a different method of interfacing with setuptools. Rather than calling "setup.py" directly, the frontend should: 1. Set the current directory to the directory with a setup.py file 2. Import this module into a safe python interpreter (one in which setuptools can potentially set global variables or crash hard). 3. Call one of the functions defined in PEP 517. What each function does is defined in PEP 517. However, here is a "casual" definition of the functions (this definition should not be relied on for bug reports or API stability): - `build_wheel`: build a wheel in the folder and return the basename - `get_requires_for_build_wheel`: get the `setup_requires` to build - `prepare_metadata_for_build_wheel`: get the `install_requires` - `build_sdist`: build an sdist in the folder and return the basename - `get_requires_for_build_sdist`: get the `setup_requires` to build Again, this is not a formal definition! Just a "taste" of the module. N)Path)DictIteratorListOptionalUnion)errors) same_path) parse_strings)SetuptoolsDeprecationWarning) strtobool) get_requires_for_build_sdistget_requires_for_build_wheel prepare_metadata_for_build_wheel build_wheel build_sdistget_requires_for_build_editable#prepare_metadata_for_build_editablebuild_editable __legacy__SetupRequirementsErrorSETUPTOOLS_ENABLE_FEATURESzlegacy-editable_-c\rSrSrSrSrg)rCcXlgN specifiers)selfr"s ڎ/builddir/build/BUILDROOT/alt-python313-setuptools-69.0.2-3.el8.x86_64/opt/alt/python313/lib/python3.13/site-packages/setuptools/build_meta.py__init__SetupRequirementsError.__init__Ds$r!N)__name__ __module__ __qualname____firstlineno__r%__static_attributes__r'r$rrCs%r'rcH\rSrSrSr\\RS55rSr g) DistributionHc@[[U55n[U5er )listr r)r#r"specifier_lists r$fetch_build_eggsDistribution.fetch_build_eggsIsmJ78$^44r'c## [RRnU[RlSv U[Rlg!U[Rlf=f7f)zW Replace distutils.dist.Distribution with this class for the duration of this context. N) distutilscorer/)clsorigs r$patchDistribution.patchNsB~~**&) # / *.INN '$INN 's0A'A A' A$$A'r-N) r(r)r*r+r4 classmethod contextlibcontextmanagerr;r,r-r'r$r/r/Hs)5  / /r'r/c## [RnS[lSv U[lg!U[lf=f7f)zTemporarily disable installing setup_requires Under PEP 517, the backend reports build dependencies to the frontend, and the frontend is responsible for ensuring they're installed. So setuptools (acting as a backend) should not try to install them. cgr r-)attrss r$+no_install_setup_requires..gstr'N) setuptools_install_setup_requires)r:s r$no_install_setup_requiresrG^s2  - -D);J&2 -1 *T *sA0 A =Ac [R"U5Vs/sHHn[RR[RR X55(dMFUPMJ sn$s snfr )oslistdirpathisdirjoin)a_dirnames r$_get_immediate_subdirectoriesrPnsIE* *bggmmBGGLL# UHoRT5(dMUv M g7fr )endswith).0f extensions r$ '_file_with_extension..usJ0aJJy4I0s) )z[No distribution was found. Ensure that `setup.py` is not empty and that it calls `setup()`.)rIrJ ValueError) directoryrVmatchingfiles ` r$_file_with_extensionr]tsLJ2::i0JH  K   8   s)?c[RRU5(d[R"S5$[ [ S[5"U5$)Nz%from setuptools import setup; setup()open)rIrKexistsioStringIOgetattrtokenizer_ setup_scripts r$_open_setup_scriptrgs9 77>>, ' '{{CDD 8VT *< 88r'c## [R"5 [R"SS5 Sv SSS5 g!,(df  g=f7f)Nignorezsetup.py install is deprecated)warningscatch_warningsfilterwarningsr-r'r$suppress_known_deprecationrms0  "*JK  # " "sA= A A Ac\rSrSrSrS\S\S\\4SjrS\S\ \4Sjr S\S\ \4Sjr S\S\ \4S jr S\S\ \4S jr S rg ) _ConfigSettingsTranslatorzTranslate ``config_settings`` into distutils-style command arguments. Only a limited number of options is currently supported. keyconfig_settingsreturncU=(d 0nURU5=(d /n[U[5(a[R"U5$U$)a Get the value of a specific key in ``config_settings`` as a list of strings. >>> fn = _ConfigSettingsTranslator()._get_config >>> fn("--global-option", None) [] >>> fn("--global-option", {}) [] >>> fn("--global-option", {'--global-option': 'foo'}) ['foo'] >>> fn("--global-option", {'--global-option': ['foo']}) ['foo'] >>> fn("--global-option", {'--global-option': 'foo'}) ['foo'] >>> fn("--global-option", {'--global-option': 'foo bar'}) ['foo', 'bar'] )get isinstancestrshlexsplit)r#rqrrcfgoptss r$ _get_config%_ConfigSettingsTranslator._get_configs@$#wws|!r$.tS$9$9u{{4 CtCr'c## U=(d 0n1SknSU;dSU;aU[URS5=(d URS5=(d S5nUR5U;aSOSv SU;dSU;aU[URS5=(d URS5=(d S5nUR5U;aSOSv URS U5S hvN g N7f) a Let the user specify ``verbose`` or ``quiet`` + escape hatch via ``--global-option``. Note: ``-v``, ``-vv``, ``-vvv`` have similar effects in setuptools, so we just have to cover the basic scenario ``-v``. >>> fn = _ConfigSettingsTranslator()._global_args >>> list(fn(None)) [] >>> list(fn({"verbose": "False"})) ['-q'] >>> list(fn({"verbose": "1"})) ['-v'] >>> list(fn({"--verbose": None})) ['-v'] >>> list(fn({"verbose": "true", "--global-option": "-q --no-user-cfg"})) ['-v', '-q', '--no-user-cfg'] >>> list(fn({"--quiet": None})) ['-q'] >0noofffalseverbosez --verbose1z-qz-vquietz--quietz--global-optionN)rwrulowerr|)r#rrrzfalseylevels r$ _global_args&_ConfigSettingsTranslator._global_argss*#,  {c1 *Icggk.BIcJE ;;=F24 = c>Y#-(ECGGI,>E#FE ;;=F24 =##$5GGGsC'C1)C/*C1c## U=(d 0nSU;a-[[US=(d S55nU(aSOSv SU;aS[US5/ShvN ggN7f)aH The ``dist_info`` command accepts ``tag-date`` and ``tag-build``. .. warning:: We cannot use this yet as it requires the ``sdist`` and ``bdist_wheel`` commands run in ``build_sdist`` and ``build_wheel`` to reuse the egg-info directory created in ``prepare_metadata_for_build_wheel``. >>> fn = _ConfigSettingsTranslator()._ConfigSettingsTranslator__dist_info_args >>> list(fn(None)) [] >>> list(fn({"tag-date": "False"})) ['--no-date'] >>> list(fn({"tag-date": None})) ['--no-date'] >>> list(fn({"tag-date": "true", "tag-build": ".a"})) ['--tag-date', '--tag-build', '.a'] ztag-daterz --tag-datez --no-datez tag-buildz --tag-buildN)rrw)r#rrrzvals r$__dist_info_args*_ConfigSettingsTranslator.__dist_info_argssc&#  CJ :7;>> fn = _ConfigSettingsTranslator()._editable_args >>> list(fn(None)) [] >>> list(fn({"editable-mode": "strict"})) ['--mode', 'strict'] z editable-mode editable_modeNz--mode)rurw)r#rrrzmodes r$_editable_args(_ConfigSettingsTranslator._editable_argssE#ww'C377?+C c$i(((sA AAAc#D# URSU5ShvN gN7f)a Users may expect to pass arbitrary lists of arguments to a command via "--global-option" (example provided in PEP 517 of a "escape hatch"). >>> fn = _ConfigSettingsTranslator()._arbitrary_args >>> list(fn(None)) [] >>> list(fn({})) [] >>> list(fn({'--build-option': 'foo'})) ['foo'] >>> list(fn({'--build-option': ['foo']})) ['foo'] >>> list(fn({'--build-option': 'foo'})) ['foo'] >>> list(fn({'--build-option': 'foo bar'})) ['foo', 'bar'] >>> list(fn({'--global-option': 'foo'})) [] z--build-optionN)r|r#rrs r$_arbitrary_args)_ConfigSettingsTranslator._arbitrary_argss*##$4oFFFs   r-N)r(r)r*r+__doc__rw_ConfigSettingsrr|rr)_ConfigSettingsTranslator__dist_info_argsrrr,r-r'r$roros DsD_DcD,HOH H@>>HSM>4)o)(3-) GG8C=Gr'roc\rSrSrSrSSjrSSjrSSjrS\S\S \4S jr S\S\S \ 4S jr SS jr S r SSjrSSjrS\\S \\4Sjr\(dSSjrSSjrSSjrSrgSrg)_BuildMetaBackendic4/[RSSQURU5QSP[l[R 5 UR 5 SSS5 U$!,(df  U$=f![ anX#R- nSnAU$SnAff=f)Nr egg_info)sysargvrr/r; run_setuprr")r#rr requirementses r$_get_build_requires%_BuildMetaBackend._get_build_requiress XXbq\    /     )##% &  &% & ) LL (L )s5A4A"A4" A1,A41A44 B>BBcx[RRU5nSn[U5nUR 5R SS5nSSS5 [ W[55 g!,(df  N$=f![a2nUR(ae[R"SSSS9 SnAgSnAff=f)N__main__z\r\nz\nz6Running `setup.py` directly as CLI tool is deprecated.znPlease avoid using `sys.exit(0)` or similar statements that don't fit in the paradigm of a configuration file.zAhttps://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html)see_url) rIrKabspathrgreadreplaceexeclocals SystemExitcoder emit)r#rf__file__r(rUrrs r$r_BuildMetaBackend.run_setup-s77??<0  )Q668##GU3D*  vx * )  vv ( - -HJ+   s#!A,A=, A:= B9(B44B9Nc$URUS/S9$)Nwheelrrrs r$r._BuildMetaBackend.get_requires_for_build_wheelDs''wi'PPr'c"URU/S9$)Nrrrs r$r._BuildMetaBackend.get_requires_for_build_sdistGs''b'IIr'metadata_directorysuffixrscURX5n[URU5(d [R"[ U5U5 UR $)z PEP 517 requires that the .dist-info directory be placed in the metadata_directory. To comply, we MUST copy the directory to the root. Returns the basename of the info directory, e.g. `proj-0.0.0.dist-info`. )_find_info_directoryr parentshutilmoverwrO)r#rrinfo_dirs r$_bubble_up_info_directory+_BuildMetaBackend._bubble_up_info_directoryJsD,,-?H*<== KKH '9 :}}r'cj[R"U5Hwup4nUVs/sHofRU5(dMUPM nn[U5S:wd[U5S:wdMO[U5S:Xd SUS35e[ X7S5s $ SUSU3n[ R "U5es snf)Nrr z Multiple z directories foundzNo z directory found in )rIwalkrSlenrr InternalError) r#rrrdirsrrU candidatesmsgs r$r&_BuildMetaBackend._find_info_directoryWs!ww'9:OF!%)@TZZ-?!TJ@:!#s4yA~:!+Sy@R-SS+FqM22 ;F8/0B/CD""3''As B0B0c /[RSSQURU5QSPSPUPSP[l[5 UR 5 SSS5 UR US5 UR US5$!,(df  N2=f)Nr dist_infoz --output-dirz--keep-egg-infoz .egg-infoz .dist-info)rrrrGrrr#rrrs r$r2_BuildMetaBackend.prepare_metadata_for_build_wheelbs XXbq\    /          ' ( NN ) &&'9;G--.@,OO ) (s A?? B c[RRU5n[R"USS9 SUS.n[R "S0UD6n/[ RSSQURU5QUQSPUP[ l[5 UR5 SSS5 [Xb5n[RRX75n[RRU5(a[R"U5 [R"[RRXg5U5 SSS5 U$!,(df  N=f!,(df  W$=f)NT)exist_okz.tmp-)prefixdirr z --dist-dirr-)rIrKrmakedirstempfileTemporaryDirectoryrrrrGrr]rMr`removerename) r# setup_commandresult_extensionresult_directoryrr temp_opts tmp_dist_dirresult_basename result_paths r$_build_with_temp_dir&_BuildMetaBackend._build_with_temp_dirss*77??+;< $t4&/?@  ( ( 59 5"1""?3   CH+, -3<RO'',,'7IKww~~k** +& IIbggll<A; O!6$-,6 5$s&AEE !B E E E E+c[5 URS/URU5QSUU5sSSS5 $!,(df  g=f)N bdist_wheel.whl)rmrr)r#wheel_directoryrrrs r$r_BuildMetaBackend.build_wheelsC( ),,G!5!5o!FG * ) )s &; A c,UR/SQSX5$)N)sdistz --formatsgztarz.tar.gz)r)r#sdist_directoryrrs r$r_BuildMetaBackend.build_sdists(( +Y  r'cU(dg[[U5RS55n[U5S::deU(a[ US5$S$)Nz *.dist-infor r)r2rglobrrw)r#rdist_info_candidatess r$_get_dist_info_dir$_BuildMetaBackend._get_dist_info_dirsP!#D);$<$A$A-$PQ'(A---/Cs'*+MMr'cURU5nU(aSU/O/nS/UQURU5Qn[5 URUSX5sSSS5 $!,(df  g=f)Nz--dist-info-direditable_wheelr)rrrmr)r#rrrrrr{cmds r$r _BuildMetaBackend.build_editablesh../ABH4<%x0"D#RdRT-@-@-QRC+-00.--s A A*c$URU5$r )rrs r$r1_BuildMetaBackend.get_requires_for_build_editables44_E Er'c$URX5$r )rrs r$r5_BuildMetaBackend.prepare_metadata_for_build_editables88" r'r-zsetup.pyr )NN)r(r)r*r+rrrrrwrrrrrrrrrLEGACY_EDITABLErrrr,r-r'r$rrs .QJ C  QT  (s (C (D (37P"<IM  NXc]NxPS}N  MQ  F7; ) r'rc0^\rSrSrSrSU4SjjrSrU=r$)_BuildMetaLegacyBackendia/Compatibility backend for setuptools This is a version of setuptools.build_meta that endeavors to maintain backwards compatibility with pre-PEP 517 modes of invocation. It exists as a temporary bridge between the old packaging mechanism and the new packaging mechanism, and will eventually be removed. c*>[[R5n[RR [RR U55nU[R;a [RR SU5 [RSnU[RS'[[U]+US9 U[RSS&U[RS'g!U[RSS&U[RS'f=f)Nrre) r2rrKrIdirnamerinsertrsuperrr)r#rfsys_path script_dir sys_argv_0 __class__s r$r!_BuildMetaLegacyBackend.run_setups>WW__RWW__\%BC SXX % HHOOAz * XXa[ "  % )4 : : U#CHHQK$CHHQK#CHHQK$CHHQKs 2C**(Dr-r)r(r)r*r+rrr, __classcell__)rs@r$rrs %%r'r)rrjpathlibrtypingrrrrrrEr7rr _pathr _reqsr r distutils.utilr__all__getenvrrrr BaseExceptionrdistr/r?rGrPr]rgrmrwrrorr_BACKENDrrrrrrrrrr-r'r$rs8  88 2$  YY'CRHNNP#'A'I'I#s'SS%]% /:??///,  2 2 9  4U3S 4+?%@ @AB |G|G~b1bJ%%/%%R  'DD'DD#+#L#L "" "" &.&N&N#*2*V*V',,N% & r'