^Qj= ddlZddlZddlZddlZddlZddlmZddlmZddlm Z ddl m Z m Z mZmZmZmZddlZddlmZe rddl mZGd d eZd eee fd ed dfdZd ed eee ffdZGddeZGddeZGddeZGddeZ d"deedeedeeeefd dfdZ d"deedeedeeeefd dfdZ!deded efdZ"Gd d!Z#y)#N)contextmanager)abspath)join) TYPE_CHECKINGAnyIteratorMappingOptionalSequence)_in_proc_script_path)Protocolc JeZdZdZ ddeedeedeeeefddfdZy) SubprocessRunnerz%A protocol for the subprocess runner.Ncmdcwd extra_environreturncyN)selfrrrs Z/home/oem/CyberBrain26-unified/.venv/lib/python3.12/site-packages/pyproject_hooks/_impl.py__call__zSubprocessRunner.__call__s NN) __name__ __module__ __qualname____doc__r strr r rrrrrrsN3 "&9=  # # $GCH$56     rrobjpathrc xt|dd5}tj||fi|dddy#1swYyxYw)Nwutf-8encoding)openjsondump)r"r#kwargsfs r write_jsonr.s8 dC' *$a #q#F#$$$s09crt|d5}tj|cdddS#1swYyxYw)Nr&r')r)r*load)r#r-s r read_jsonr1"s. dW %yy|s-6ceZdZdZy)BuildBackendWarningzBWill be emitted for every UserWarning emitted by the hook process.N)rrrr rrrr3r3'sLrr3c XeZdZdZ d dedeedeedeeeddf fd ZxZS) BackendUnavailablezEWill be raised if the backend cannot be imported in the hook process.N tracebackmessage backend_name backend_pathrc||_||_|xsd|_t||xsd|jrd|jzydzy)NzError while importing backendz Traceback: )r8r9r6super__init__)rr6r7r8r9 __class__s rr=zBackendUnavailable.__init__.sc)("b 99:6:nn!$..!12 N JL N rNNN) rrrr r!r r r= __classcell__r>s@rr5r5+s\O "&&*04   # sm  x}-     rr5c,eZdZdZdeddffd ZxZS) HookMissingz>Will be raised on missing hooks (if a fallback can't be used). hook_namerNc2t||||_yr)r<r=rD)rrDr>s rr=zHookMissing.__init__Bs #"r)rrrr r!r=r@rAs@rrCrC?sH###$##rrCc eZdZdZdeddfdZy)UnsupportedOperationzDMay be raised by build_sdist if the backend indicates that it can't.r6rNc||_yr)r6)rr6s rr=zUnsupportedOperation.__init__Js "r)rrrr r!r=rrrrGrGGsN###$#rrGrrrctjj}|r|j|t j |||dy)zpThe default method of calling the wrapper subprocess. This uses :func:`subprocess.run` under the hood. T)renvcheckN)osenvironcopyupdate subprocessrunrrrrJs rdefault_subprocess_runnerrSNs5 **// C =!NN3CS5rctjj}|r|j|t j |||tj tjdy)zCall the subprocess while suppressing output. This uses :func:`subprocess.run` with `stdout=PIPE, stderr=STDOUT` under the hood. T)rrJstdoutstderrrKN)rLrMrNrOrPrQPIPESTDOUTrRs rquiet_subprocess_runnerrY^sM **// C =!NN     r source_tree requestedctjj|r tdtjj |}tjj tjj ||}tjj|}tjj|}tjj||g|k7r td|S)zNormalise and check a backend path. Ensure that the requested backend path is specified as a relative path, and resolves to a location under the given source tree. Return an absolute version of the requested path. zpaths must be relativez paths must be inside source tree) rLr#isabs ValueErrorrnormpathrnormcase commonpath)rZr[ abs_source abs_requested norm_sourcenorm_requesteds rnorm_and_checkrfvs ww}}Y122-JGG$$RWW\\*i%HIM''"":.KWW%%m4N ww;78KG;<< rc eZdZdZ ddededeeededdeed df d Zeddd e dfd Z d eefd Z dd ee ee fd eefdZ dded ee ee fded efdZ d ded ee ee fdeed efdZ dd ee ee fd eefdZ dded ee ee fded efdZ d ded ee ee fdeed efdZ dd ee ee fd eefdZ dded ee ee fd efdZdede ee fd e fdZy)!BuildBackendHookCallerzAA wrapper to call the build backend hooks for a source directory.N source_dir build_backendr9runnerrpython_executablerc|t}t||_||_|r#|Dcgc]}t |j|}}||_||_|stj}||_ ycc}w)a :param source_dir: The source directory to invoke the build backend for :param build_backend: The build backend spec :param backend_path: Additional path entries for the build backend spec :param runner: The :ref:`subprocess runner ` to use :param python_executable: The Python executable used to invoke the build backend N) rSrrirjrfr9_subprocess_runnersys executablerl)rrirjr9rkrlps rr=zBuildBackendHookCaller.__init__sn >.F!*-* HTU1N4??A>ULU("( # !2 VsA-c#bK|j}||_ d||_y#||_wxYww)aA context manager for temporarily overriding the default :ref:`subprocess runner `. :param runner: The new subprocess runner to use within the context. .. warning:: This context manager temporarily mutates the hook caller instance and is not thread-safe. Callers that need to run hooks concurrently should create separate :class:`BuildBackendHookCaller` instances, or provide the subprocess runner when constructing the caller. .. code-block:: python hook_caller = BuildBackendHookCaller(...) with hook_caller.subprocess_runner(quiet_subprocess_runner): ... N)rn)rrkprevs rsubprocess_runnerz(BuildBackendHookCaller.subprocess_runners3(&&"( + &*D #dD #s/#/ ,/c&|jdiS)z>Return the list of optional features supported by the backend._supported_features _call_hook)rs rrvz*BuildBackendHookCaller._supported_featuress4b99rconfig_settingsc*|jdd|iS)amGet additional dependencies required for building a wheel. :param config_settings: The configuration settings for the build backend :returns: A list of :pep:`dependency specifiers <508>`. .. admonition:: Fallback If the build backend does not defined a hook with this name, an empty list will be returned. get_requires_for_build_wheelryrwrrys rr{z3BuildBackendHookCaller.get_requires_for_build_wheels  *->,P  rmetadata_directory_allow_fallbackc@|jdt|||dS)aSPrepare a ``*.dist-info`` folder with metadata for this project. :param metadata_directory: The directory to write the metadata to :param config_settings: The configuration settings for the build backend :param _allow_fallback: Whether to allow the fallback to building a wheel and extracting the metadata from it. Should be passed as a keyword argument only. :returns: Name of the newly created subfolder within ``metadata_directory``, containing the metadata. .. admonition:: Fallback If the build backend does not define a hook with this name and ``_allow_fallback`` is truthy, the backend will be asked to build a wheel via the ``build_wheel`` hook and the dist-info extracted from that will be returned. prepare_metadata_for_build_wheelr}ryr~rxrrr}ryr~s rrz7BuildBackendHookCaller.prepare_metadata_for_build_wheels,0 .&-.@&A#2#2   rwheel_directorycZ| t|}|jdt|||dS)aBuild a wheel from this project. :param wheel_directory: The directory to write the wheel to :param config_settings: The configuration settings for the build backend :param metadata_directory: The directory to reuse existing metadata from :returns: The name of the newly created wheel within ``wheel_directory``. .. admonition:: Interaction with fallback If the ``build_wheel`` hook was called in the fallback for :meth:`prepare_metadata_for_build_wheel`, the build backend would not be invoked. Instead, the previously built wheel will be copied to ``wheel_directory`` and the name of that file will be returned. build_wheelrryr}rrxrrryr}s rrz"BuildBackendHookCaller.build_wheels=*  )!();!<  #*?#;#2&8   rc*|jdd|iS)awGet additional dependencies required for building an editable wheel. :param config_settings: The configuration settings for the build backend :returns: A list of :pep:`dependency specifiers <508>`. .. admonition:: Fallback If the build backend does not defined a hook with this name, an empty list will be returned. get_requires_for_build_editableryrwr|s rrz6BuildBackendHookCaller.get_requires_for_build_editables  -0A?/S  rc@|jdt|||dS)aUPrepare a ``*.dist-info`` folder with metadata for this project. :param metadata_directory: The directory to write the metadata to :param config_settings: The configuration settings for the build backend :param _allow_fallback: Whether to allow the fallback to building a wheel and extracting the metadata from it. Should be passed as a keyword argument only. :returns: Name of the newly created subfolder within ``metadata_directory``, containing the metadata. .. admonition:: Fallback If the build backend does not define a hook with this name and ``_allow_fallback`` is truthy, the backend will be asked to build a wheel via the ``build_editable`` hook and the dist-info extracted from that will be returned. #prepare_metadata_for_build_editablerrrs rrz:BuildBackendHookCaller.prepare_metadata_for_build_editable/s,. 1&-.@&A#2#2   rcZ| t|}|jdt|||dS)aBuild an editable wheel from this project. :param wheel_directory: The directory to write the wheel to :param config_settings: The configuration settings for the build backend :param metadata_directory: The directory to reuse existing metadata from :returns: The name of the newly created wheel within ``wheel_directory``. .. admonition:: Interaction with fallback If the ``build_editable`` hook was called in the fallback for :meth:`prepare_metadata_for_build_editable`, the build backend would not be invoked. Instead, the previously built wheel will be copied to ``wheel_directory`` and the name of that file will be returned. build_editablerrrs rrz%BuildBackendHookCaller.build_editableOs=,  )!();!<  #*?#;#2&8   rc*|jdd|iS)zGet additional dependencies required for building an sdist. :returns: A list of :pep:`dependency specifiers <508>`. get_requires_for_build_sdistryrwr|s rrz3BuildBackendHookCaller.get_requires_for_build_sdistps  *->,P  rsdist_directoryc>|jdt||dS)zBuild an sdist from this project. :returns: The name of the newly created sdist within ``sdist_directory``. build_sdist)rryr)rrrys rrz"BuildBackendHookCaller.build_sdist|s( #*?#;#2   rrDr,c d|ji}|jr"tj|j|d<t j 5}d|i}t |t|ddt5}|j}|j|tt|||g|j|dddtt|d}|jd rt!|jd d |jd rCt#|jd d |jd d |j|j|jdrt%|jdxs||jdgD](} t'j(| dt*| d| d*|dcdddS#1swYxYw#1swYyxYw)N_PYPROJECT_HOOKS_BUILD_BACKEND"_PYPROJECT_HOOKS_BACKEND_PATH_JSONr,z input.json)indent)rrz output.json unsupportedr6r; no_backend backend_error)r7r8r9 hook_missingmissing_hook_namewarningsr7filenamelineno)r7categoryrr return_val)rjr9r*dumpstempfileTemporaryDirectoryr.pjoinr rlrnrr!rir1getrGr5rCr warn_explicitr3) rrDr,rtd hook_inputscriptpythondatar%s rrxz!BuildBackendHookCaller._call_hooks94;M;MN   BF**!!CM> ? ( ( *! &b"F+J z5\#:1 E&' 6//''WS[19bA"/( U2}56Dxx &*488K+DEExx %(HH["- HH_b9!%!3!3!%!2!2  xx'!$((+>"?"L9MMXXj"- &&iL0z]X;   %C! &! &    ! &! &s&'G8AG9D GG GG&r?r)NTr)rrrr r!r r r=rrrtrvr rr{boolrrrrrrrrxrrrrhrhsK 15/3+/ 333x}- 3 +, 3 $C= 3 3:+(:+x~++4:Xc]: 8< !'#s("34  # *8< $   "'#s("34    H8<,0   "'#s("34 %SM   D8< !'#s("34  # *8< $   "'#s("34    F8<,0   "'#s("34 %SM   F8<  !'#s("34   #  8<  "'#s("34   $)&C)&c1B)&s)&rrhr)$r*rLrorrP contextlibros.pathrrrtypingrrrr r r r _in_processr rrr!r.r1 UserWarningr3 Exceptionr5rCrGrSrYrfrhrrrrs` %!LL- 8 $GCH%$S$t$ CGCH- M+M  (#)##9#15 6 # 6 # 6GCH-. 6 6$15 # #GCH-. 0*l&l&r