+ 4jnrRt^RIHt^RIt^RIt^RIt^RIt^RIt^RIt^RI t ^RI H t ^RI H t HtHt^RIHt^RIHtHt^RIt^RIHt^RIHt^R IHt^R IHt^R IH t ^R I!H"t"^R I#H$t$^RI%H&t&^RI'H(t(H)t)^RI*H+t+^RI,H-t-H.t.H/t/^RI0H1t1^RI2H3t3]'dG^RI4H5t5H6t6H7t7^RI8H9t9^RI:H;t;^RIH?t?^RI%H@t@HAtA^RI*HBtBHCtCHDtDHEtE^RIFHGtG]!R]A]@4tHR.tI] !RR]44tJ]P!]L4tM]PR 8Xd]PR?8dR!M]PR 8XdR"MR#tPR$tQ!R%R&]R4tS]T]UR'3,tVR(R)ltW] !R*R*R+7!R,R-44tX!R.R4tYR/R0ltZR1R2lt[R3R4lt\R5R6lt]R7R8lt^R9R:lt_R;R<lt`R=R>ltaR#)@aIsolated build env that uses nab itself plus the PyPA ``installer``. ``NabBuildEnv`` implements ``build.env.IsolatedEnv`` so it slots into ``build.ProjectBuilder.from_isolated_env``. The pieces: * ``venv.EnvBuilder`` (stdlib) creates an empty interpreter at a temp path, ``with_pip=False``; nab does not need pip in there. * nab's own resolver picks versions for ``[build-system].requires`` using the same indexes / ``uploaded-prior-to`` window as the outer resolve. * ``download_lock`` from :mod:`nab_python.download` fetches the resolved wheels into a temp directory. * :func:`installer.install` writes each wheel into the venv via ``installer.SchemeDictionaryDestination``, configured from the venv's own scheme paths. The env is a context manager. Entering it builds the venv and installs the requirements; exiting removes the temp tree. The ``python_executable`` and ``make_extra_environ`` properties come from ``build.env.IsolatedEnv``. ) annotationsN)suppress) dataclassfieldreplace)Path) TYPE_CHECKINGTypeVar)install)SchemeDictionaryDestination) WheelFile)extract_sdist_archive)Urllib3AsyncTransport)UnsupportedVcsErrorcanonicalize_name)NabProjectConfig) DownloadError download_lock)IndexPin) BuildPolicy DistPolicyMissingExtraError)InvalidProjectRequirementError)BuildBackendError)CallableIterableMapping) RecordEntry)Scheme)Self)AsyncHttpTransport) IndexOverridePackageOverride) LockInputPinShape SdistArtifact TargetLock)TagSet _OverrideT NabBuildEnvcfa]tRt^Jt$Rt]!]RRR7tR]R&RV3Rllt RV3R llt R t V;t #) _FastSchemeDictionaryDestinationa``SchemeDictionaryDestination`` that skips bytecode-compile work. The stock ``_compile_bytecode`` always resolves the target file's real path before checking ``bytecode_optimization_levels``; with an empty levels tuple, the loop body never runs but the resolve still hits the filesystem twice per record. Skipping the early work when the levels tuple is empty is safe because the body would have been a no-op. ``written`` records ``(scheme root, path within it)`` for every file the install writes, so a later install can remove them. F)default_factoryinitreprlist[tuple[Path, Path]]writtenc$V^8dQhRRRRRR/#)schemerrecordrreturnNone)formats"g/home/user/pdf2html-billing-ledger-validate/.venv/lib/python3.14/site-packages/nab_python/_build/env.py __annotate__-_FastSchemeDictionaryDestination.__annotate__]s!222 22c N<VP'gR#\SV` W4R#N)bytecode_optimization_levelssuper_compile_bytecode)selfr4r5 __class__s&&&r:rB2_FastSchemeDictionaryDestination._compile_bytecode]s000  !&1r=c(V^8dQhRRRRRRRR/#) r3r4rrecord_file_pathstrrecordsz$Iterable[tuple[Scheme, RecordEntry]]r6r7r8)r9s"r:r;r<bs8 I I I I6 I  Ir=c <\V4pVUUu.uF6wrV\VPV,4\VP43NK8 uppVn\ SV`WV4R#uuppir?)listr scheme_dictpathr1rAfinalize_installation)rCr4rGrIentries entry_schemeentryrDs&&&& r:rN6_FastSchemeDictionaryDestination.finalize_installationbsfw-(/ '.# $""<0 14 3C D'.  %fH  sDD!c V^8dQhRRRR/#)r3argsobjectr6r7r8)r9s"r:r;ru/s  f  r=c hVPe$VPP4RVnR#R#)z?Remove the temp tree that holds the venv and downloaded wheels.N)r}r)rCrs&*r:__exit__NabBuildEnv.__exit__/s( << # LL "DL $r=cV^8dQhRR/#)r3r6rHr8)r9s"r:r;ru6s,,3,r=c bVPfRp\V4h\VP4#)z:Path to the venv's interpreter (str, per ``IsolatedEnv``).2NabBuildEnv used outside its context-manager scope)rr^rH)rCrs& r:python_executableNabBuildEnv.python_executable5s1  " " *FC$ $4**++r=cV^8dQhRR/#)r3r6zMapping[str, str]r8)r9s"r:r;ru=s44$54r=c VPfRp\V4h\PP R4pV'd!VP \P V 2M\ VP4pRVRR/#)aPATH / PYTHONPATH overrides for the build subprocess. Prepends the venv's scripts dir so build backends find their installed entry points; clears ``PYTHONPATH`` so the host's ``sys.path`` does not leak in (matches the convention used by ``build.env.DefaultIsolatedEnv``). rPATH PYTHONPATH)rr^osenvirongetpathseprH)rCr host_pathnew_paths& r:make_extra_environNabBuildEnv.make_extra_environ=sx    $FC$ $JJNN6*   !"**i[ 9T&&'  ,33r=c V^8dQhRRRR/#)r3 requirementsrqr6r7r8)r9s"r:r;ruPsWWIW$Wr=c VPeVPfRp\V4hV'gR#VPPR, pVR\ \ VP 444 2, pVPRRR7VPWAR7pVPV\VP44R#)aInstall additional requirements into the live env. Used for ``get_requires_for_build_wheel`` follow-up requests (the backend asks for additional deps after the env is already up). The inner resolve runs over ``requires`` and ``requirements`` together, so its result is the whole build env rather than an addition to it: it can pin a different version of something already installed, or drop it. Nrr_extra_Tparentsexist_ok)extra) r~rr^rlenrKiterdirrrrr)rCrrrsubrs&& r:r NabBuildEnv.installPs ?? "d&=&=&EFC$ $ OO**X5 GCY->->-@(A$B#CDD $ .000I  [*3dpR T 2p\T4ThRp?ii;i \DdpRT 2p\T4ThRp?ii;iuupi)asResolve ``requires`` (+ ``extra``) and write wheels under ``wheel_dir``. The inner resolve runs against a synthetic pyproject so it can reuse :func:`nab_python.resolve.resolve_for_targets` and :func:`nab_python.download.download_lock` end-to-end. No local sources / workspace / marker overlay; build deps come from the configured indexes only. It admits wheels and sdists, like any resolve, so the version it settles on is the one the requirement asked for rather than the newest that happens to publish a wheel. Whether a version without an installable wheel can be used is :meth:`_plan_install`'s decision, taken once the resolve has named it. It reads metadata statically: its build policy is ``never`` and no inherited override may raise it. A backend invocation to learn a build requirement's dependencies would be a second recursion, one the depth budget does not count. )build_lock_inputresolve_for_targetsz, z0build requirements unavailable in offline mode: _inner_projectTrzpyproject.tomlzutf-8)encodingc38"TFp\V4xK R#5ir?)_without_build_permission).0overrides& r: 4NabBuildEnv._resolve_and_download..s$ >H*(33 >s)indexespackage_overridesindex_overridesuploaded_prior_to dist_policy build_policy)rrzbuild env resolve failed: Nzbuild env download failed: z.whlc3H<"TFpSPVS4xK R#5ir?)_build_requirement)rpendingrCrs& r:rrs$ GOGD # #GY 7 7xs")&resolverrrKrwrryjoinr^rr write_text_render_synthetic_pyprojectrrxrr{rritemsrrrWHEEL_OR_SDISTrNEVERrzraise_for_failurerNotImplementedErrorrr _plan_installrrr1skippedsuffix)rCrrrrrpjoinedr synthetic_dir syntheticr`r inner_config transportresultr lock_inputto_builddownload_result all_pathsprsff$ r:r!NabBuildEnv._resolve_and_downloadgs: D'  OOE " ===YYx(FDVHMC$ $!((+;; D48!$44 8BWU'LL((#e$ $ > >$ee$ $ > >$ '+ll&B&B&H&H&J&JND/99&J#ll<<"11$**  "++-  .(#F  $ $ & $11 V 9  H .+J 9MO001D9P9P4QQ &=Y!((f*sB I$/I*& J&K>K*JJJ J?)J::J?cV^8dQhRR/#)r3r6intr8)r9s"r:r;rusDDsDr=c bVPP\VP4, #)z8How many more build envs may be opened beneath this one.)rxbuild_requires_depthrr|rs&r: _build_budgetNabBuildEnv._build_budgets"||003t{{3CCCr=c V^8dQhRRRR/#)r3r r$r6z%tuple[LockInput, list[_PendingBuild]]r8)r9s"r:r;rus>>#> .>r=c "/p.pVPP4F`wrE/pVPP4F-wrxVPWPP V4Wg&K/ \ WVR7W$&Kb \ WR7V3#)aDecide how each pin reaches the env, and narrow it to that artifact. A pin with a wheel the host accepts is narrowed to that one wheel: a lock records every wheel of the pinned version the target admits, which can be several (the tiered manylinux aliases, or a ``py3-none-any`` beside a platform wheel), and the env installs one. Narrowing is for the download and the install; a written lock keeps every wheel, so one lock stays portable across targets. A pin with no such wheel has to be built, and comes back in the second element with its wheels dropped so only its sdist is fetched. Refusing that build is this method's other job: it raises rather than leaving a requirement quietly uninstalled, because the backend would then fail on an import error that names nothing useful. )pins)targets)rrr _planned_pintargettagsr) rCr plannedr rilockrr`pins && r:rNabBuildEnv._plan_installs(*,(*%--335KE(*D!YY__. !..sKK4D4DhO /$T5GN 6 z3X==r=c(V^8dQhRRRRRRRR/#)r3r!r%rr(r zlist[_PendingBuild]r6r8)r9s"r:r;rus,0'0'0'#)0'5H0' 0'r=c \V\4'gV#VP'dVPVP4MRpVe\ W3RR7#\ VP VP4pVPpVPfV R\V4 2p\V4hWV9d$RRP.VOVN4 2p\V4hVP^8:d2V RVPP \V4 2p\V4hVP!\#WQPR74\ VR R7#) a/Return ``pin`` narrowed to the artifact the env will install. Appends to ``to_build`` when the answer is the sdist, so the caller knows which pins still owe it a build. The wheel is chosen by the target's tags rather than by the provider's ``pick_dist``. That one answers whose METADATA the pin has to satisfy, so between wheels the tags rank equally it takes the one carrying a :pep:`658` sidecar, and it may answer with an sdist or with a wheel this host cannot install. An install has none of those outs: it must be the wheel :pep:`425` ranks highest. N)rrjzF publishes no wheel this build host can install, and no sdist to buildzcyclic build requirement:  -> zx publishes no wheel this build host can install, so satisfying it means building it; [tool.nab].build-requires-depth is )rirj)rr8) isinstancerrpickrrdr`rar|rj _chain_suffixr^rrrxrappendrh)rCr!rr  preferredrirnrs&&&& r:rNabBuildEnv._planned_pins9 #x((J-0ZZZDIIcjj)T  3|4@ @CHHckk2  99 '))6u)=(>@  $ $ >.v{{?U?E?/K.LMC$ $    "'||889-:N9OQ   $ $ ECDs2&&r=c$V^8dQhRRRRRR/#)r3rrhrrr6r8)r9s"r:r;ru%s!#2#2-#2D#2T#2r=c  ^RIHpVPpW!PP, p\ P RV4VP4p\P!RR7;_uu_4p \T\T 44p T!T TTPTP .TP"OTN5R 7uuRRR4# \dpRT RT RT 2p\T4ThRp?ii;i \dpRT R T 2p\T4ThRp?ii;i \$dpRT R T 2p\T4ThRp?ii;i +'giR#;i) zBuild the downloaded sdist of ``pending`` and return the wheel's path. The wheel lands beside the downloaded artifacts, which live as long as the env does. )build_wheel_for_installz#building %s to populate a build envzbuild requirement z could not be read at rNznab-build-req-rz could not be extracted: ) output_dirrrrlrnz could not be built: )runnerr.rirjfilenamerinfo read_bytesrr^rrr r ValueErrorrxryr|r) rCrrr.riarchivedatarrtd source_dirs &&& r:rNabBuildEnv._build_requirement%sQ 4 mm444 95A .%%'D  ( (0@ A AR 224bB  2.(<< MM/DKK// B A  .&ug-CG9BseTC$# - . 2*5'1J3%P#C(c1 2% 2*5'1FseL#C(c1 2B A As`C5D?7C1 /D C.C))C.1 D<DDD? D<#D77D<<D?? E ) r|rxrryrrwrr}rzr~r8)rSrTrUrVrWrrrrrrpropertyrrr rrrrrrYr8r=r:r*r*s D<  < ?T <<, R4(2T ,,4&W.g#' gRDD><0'd#2#2r=c V^8dQhRRRR/#)r3rnrtr6rHr8)r9s"r:r;r;Ks>>>>r=c@V'dRRPV4 R2#R#)zCRender ``chain`` for an error message, or nothing when it is empty.z (chain: r%)r)r)rns&r:r(r(Ks"05Yv{{5)*! ,=2=r=c V^8dQhRRRR/#)r3rr)r6r8)r9s"r:r;r;Ps 0 0 0z 0r=cbVPR\P39dV#\VRR7#)a6Return ``override`` with any build permission it grants removed. An override reaches the build env's own resolve, where the build policy is ``never``. Letting one raise it there would start a backend invocation nothing counts against the depth budget, so a permission is dropped and only a refusal survives. N)r)rrrr)rs&r:rrPs/{'8'8 99 8$ //r=c V^8dQhRRRR/#)r3rOr0r6r7r8)r9s"r:r;r;]s!!2!t!r=c~a\4p\4pVFwopSV, pVPRR7VPR8XdZVPR, pVP VP R24FpVP4K VP V4VP S4VPV3RlVP44K \W, RRR7F3p\\4;_uu_4VP4R R R 4K5 R # +'giKJ;i) aDelete installed files and their bytecode, and directories left empty. ``entries`` are ``(scheme root, path within it)`` pairs. The scheme roots stay, as does any directory still holding something the install did not write. Cached bytecode goes with its source file: the backend has already run in this venv, so a removed package has usually been imported, and the ``__pycache__`` that import wrote would keep its directory importable as a namespace package. T) missing_okz.py __pycache__z.*.pycc36<"TFpSV, xK R#5ir?r8)rrrs& r:r _remove_files..wsH7GV4&==7Gsc,\VP4#r?)rparts)rMs&r:_remove_files..{s c$**or=)keyreverseN) setunlinkrrglobstemaddupdatersortedrrrmdir) rO directoriesrootsrelativercachecompiled directoryrs & @r:rr]s!UKuE!h  & ==E !MMM1E!JJ&++f'=>!? OOE " $Hx7G7GHH"!=t g   OO    s D++ D< c V^8dQhRRRR/#)r3 venv_pathrr6r8)r9s"r:r;r;s((D(T(r=cl\PR8XdVR, R, #VR, R, #)zEReturn the venv interpreter path (``Scripts\python.exe`` on Windows).r[Scriptsz python.exebinpythonsysplatform)r[s&r:rrs. ||w9$|33 u x ''r=c V^8dQhRRRR/#)r3rrr6rr8)r9s"r:r;r;s!!$!>!r=c \P!\V4R\.RRRR7p\P!TP4p\TR,4p\\TR,R R R TR , 244TR &T# \\P 3dpRT 2p\ T4ThRp?ii;i \PdpRT 2p\ T4ThRp?ii;i)aAsk the venv's interpreter for the scheme paths ``installer`` writes to. Subprocessing the venv guarantees the returned paths reflect the venv's layout (``site-packages`` under the venv root, scripts in its ``bin``/``Scripts`` dir, etc.) regardless of how nab itself was installed. One subprocess per env construction; negligible. ``sysconfig`` has no ``headers`` scheme, and its ``include`` names the base interpreter rather than the venv, so the header root comes from the venv's own prefix instead. z-cT)capture_outputtextcheckz%build venv interpreter probe failed: Nz7build venv interpreter probe returned non-JSON output: pathsrincludesiter_ py_versionheaders) subprocessrunrH _SCHEME_PROBErCalledProcessErrorr^jsonloadsstdoutJSONDecodeErrordictr)rr rrproberhs& r:rrs * " #T= 9  * 6==) !w0E U8_i6% :M9N1OPE) L Z22 3*5cU;C c)*   *GuMC c)*s.*B C B='B88B=C+C&&C+c$V^8dQhRRRRRR/#)r3rrrrHr6r8)r9s"r:r;r;s$ 03r=cZ\V4p\\VR,V44VR&V#)zEScheme paths for one wheel; its headers go in a directory of its own.rl)rurHr)rrrhs&& r:rrs.  E4i 0,?@E) Lr=cV^8dQhRR/#)r3r6rsr8)r9s"r:r;r;s##D#r=c(\PR8g#)zB``venv.EnvBuilder(symlinks=...)`` heuristic; avoids Windows traps.r[r`r8r=r:rrs <<7 ""r=c V^8dQhRRRR/#)r3rprqr6rHr8)r9s"r:r;r;s)r=c >\P!RRRRRRV//4#)aRender a tiny pyproject.toml whose deps are ``requires``. Used as input to the inner resolve; the on-disk file is discarded with the rest of the temp tree. The dummy name and version make the inner resolver happy without depending on the outer project's name/version. projectr`_nab_build_envraz0.0.0 dependencies)tomli_wdumps)rps&r:rrs2 == (7  r=l)brW __future__rrqloggingrrmrarr contextlibr dataclassesrrrpathlibrtypingrr r installerr rinstaller.destinationsr installer.sourcesr nab_index.clientr !nab_index.urllib3_async_transportr_vcs_admissionr_vendor.packaging.utilsrrrrdownloadrrlockfilerproviderrrrrequirements_filererrorsrcollections.abcrrrinstaller.recordsrinstaller.utilsrtyping_extensionsr nab_index.transportr!r"r#r$r%r&r'rr(r)__all__r, getLoggerrSrrbmaxsizerrorr^r{rHrtrdrhr*r(rrrrrrrr8r=r:rs,#    11)2>'2C07%3AA>%;;-&&67II FJ   $I'B$I $IN   8 $  ||w3;;#6 ||w    I38_ 2  $d#$a2a2H > 0!H(!H# r=