U âQab}%ã@s dZddlZddlZddlZddlZddlZddlZddlZddlZddl m Z ddl m Z ddl mZdddd d d d gZGd d „d eƒZGdd„dejjƒZdd„Zdd„Zdd„Zdd„ZGdd„deƒZGdd„deƒZeƒZejZejZejZejZej Z eƒZ!dS)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)ÚTemporaryDirectory)Úparse_requirements)ÚmakedirsÚget_requires_for_build_sdistÚget_requires_for_build_wheelÚ prepare_metadata_for_build_wheelÚ build_wheelÚ build_sdistÚ __legacy__ÚSetupRequirementsErrorc@seZdZdd„ZdS)r cCs ||_dS©N)Ú specifiers)Úselfr ©rú9/usr/lib/python3.8/site-packages/setuptools/build_meta.pyÚ__init__4szSetupRequirementsError.__init__N)Ú__name__Ú __module__Ú __qualname__rrrrrr 3sc@s&eZdZdd„Zeejdd„ƒƒZdS)Ú DistributioncCstttt|ƒƒƒ}t|ƒ‚dSr )ÚlistÚmapÚstrrr )rr Zspecifier_listrrrÚfetch_build_eggs9szDistribution.fetch_build_eggsccs*tjj}|tj_z dVW5|tj_XdS)zw Replace distutils.dist.Distribution with this class for the duration of this context. N)Ú distutilsZcorer)ÚclsZorigrrrÚpatch>s  zDistribution.patchN)rrrrÚ classmethodÚ contextlibÚcontextmanagerrrrrrr8srcCs*tjddkr&t|tƒs&| t ¡¡S|S)z‘ Convert a filename to a string (on Python 2, explicitly a byte string, not Unicode) as distutils checks for the exact type str. ré)ÚsysÚ version_infoÚ isinstancerÚencodeÚgetfilesystemencoding)ÚsrrrÚ_to_strNsr'cs‡fdd„t ˆ¡DƒS)Ncs&g|]}tj tj ˆ|¡¡r|‘qSr)ÚosÚpathÚisdirÚjoin)Ú.0Úname©Za_dirrrÚ \sÿz1_get_immediate_subdirectories..©r(Úlistdirr.rr.rÚ_get_immediate_subdirectories[sr2cs"‡fdd„t |¡Dƒ}|\}|S)Nc3s|]}| ˆ¡r|VqdSr ©Úendswith©r,Úf©Ú extensionrrÚ as ÿz'_file_with_extension..r0)Z directoryr8ZmatchingÚfilerr7rÚ_file_with_extension`s  ÿr;cCs&tj |¡st d¡Sttdtƒ|ƒS)Nz%from setuptools import setup; setup()Úopen)r(r)ÚexistsÚioÚStringIOÚgetattrÚtokenizer<©Ú setup_scriptrrrÚ_open_setup_scriptis  rDc@s`eZdZdd„Zdd„Zddd„Zdd d „Zdd d „Zdd d„Zdd„Z ddd„Z ddd„Z dS)Ú_BuildMetaBackendcCs|pi}| dg¡|S)Nú--global-option)Ú setdefault©rÚconfig_settingsrrrÚ _fix_configss z_BuildMetaBackend._fix_configc Csz| |¡}tjdd…dg|dt_z t ¡�| ¡W5QRXWn,tk rt}z||j7}W5d}~XYnX|S)NéZegg_inforF)rJr!ÚargvrrÚ run_setupr r )rrIÚ requirementsÚerrrÚ_get_build_requiresxs ÿ z%_BuildMetaBackend._get_build_requiresúsetup.pyc CsD|}d}t|ƒ�}| ¡ dd¡}W5QRXtt||dƒtƒƒdS)NÚ__main__z\r\nz\nÚexec)rDÚreadÚreplacerSÚcompileÚlocals)rrCÚ__file__rr6ÚcoderrrrM…s  z_BuildMetaBackend.run_setupNcCs| |¡}|j|dgd�S)NZwheel©rN©rJrPrHrrrr�s z._BuildMetaBackend.get_requires_for_build_wheelcCs| |¡}|j|gd�S)NrZr[rHrrrr”s z._BuildMetaBackend.get_requires_for_build_sdistcCs°tjdd…ddt|ƒgt_| ¡|}dd„t |¡Dƒ}t|ƒdkrxtt|ƒƒdkrxtj  |t |¡d¡}q*qxq*||kr¨t   tj  ||d¡|¡t j |dd�|dS) NrKZ dist_infoz --egg-basecSsg|]}| d¡r|‘qS)z .dist-infor3r5rrrr/ s ÿzF_BuildMetaBackend.prepare_metadata_for_build_wheel..rT)Ú ignore_errors) r!rLr'rMr(r1Úlenr2r)r+ÚshutilZmoveZrmtree)rÚmetadata_directoryrIZdist_info_directoryZ dist_infosrrrr˜s,ÿ ÿ ÿþz2_BuildMetaBackend.prepare_metadata_for_build_wheelc Cs¬| |¡}tj |¡}t|dd�t|d��v}tjdd…|d|g|dt_| ¡t ||ƒ}tj  ||¡}tj  |¡rˆt  |¡t  tj  ||¡|¡W5QRX|S)NT)Úexist_ok)ÚdirrKz --dist-dirrF)rJr(r)Úabspathrrr!rLrMr;r+r=ÚremoveÚrename)rZ setup_commandZresult_extensionZresult_directoryrIZ tmp_dist_dirZresult_basenameZ result_pathrrrÚ_build_with_temp_dir·s     ÿþ    z&_BuildMetaBackend._build_with_temp_dircCs| dgd||¡S)NZ bdist_wheelz.whl©re)rZwheel_directoryrIr_rrrrÎs ÿz_BuildMetaBackend.build_wheelcCs| dddgd||¡S)NZsdistz --formatsZgztarz.tar.gzrf)rZsdist_directoryrIrrrr Ós  þz_BuildMetaBackend.build_sdist)rQ)N)N)N)NN)N) rrrrJrPrMrrrrerr rrrrrEqs  ÿ ÿ rEcs"eZdZdZd‡fdd„ Z‡ZS)Ú_BuildMetaLegacyBackendaCCompatibility 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. rQc sbttjƒ}tj tj |¡¡}|tjkr6tj d|¡ztt|ƒj |d�W5|tjdd…<XdS)NrrB) rr!r)r(ÚdirnamerbÚinsertÚsuperrgrM)rrCZsys_pathZ script_dir©Ú __class__rrrMás  ÿÿ z!_BuildMetaLegacyBackend.run_setup)rQ)rrrÚ__doc__rMÚ __classcell__rrrkrrgÙsrg)"rmr>r(r!rAr^rZ setuptoolsrZsetuptools.py31compatrZ pkg_resourcesrZpkg_resources.py31compatrÚ__all__Ú BaseExceptionr Zdistrr'r2r;rDÚobjectrErgZ_BACKENDrrrrr r rrrrÚsD   ú  h