`gj#dZddlmZddlZddlZddlZddlZddlZddlZddl m Z ddl m Z ddl mZejeZddZddZGd d eZdd Zd Zdd ZddZddZddZdddZy)uManaged uv — one path, no guessing. Hermes owns its own uv binary at ``$HERMES_HOME/bin/uv`` (or ``uv.exe`` on Windows). Every code path that needs uv resolves it from that single location. If the binary is missing, ``ensure_uv()`` bootstraps it via the official standalone installer with ``UV_UNMANAGED_INSTALL`` / ``UV_INSTALL_DIR`` pointed at ``$HERMES_HOME/bin`` so the installer writes directly there — no PATH probing, no conda guards, no multi-location resolution chains. ) annotationsN)Path)Optional)get_hermes_homecdt}tjdk(r|dz dz S|dz dz S)uReturn the path where Hermes keeps *its* uv binary. ``$HERMES_HOME/bin/uv`` on POSIX, ``$HERMES_HOME\bin\uv.exe`` on Windows. The directory may not exist yet — callers should use ``ensure_uv()`` to bootstrap it. Windowsbinzuv.exeuv)rplatformsystem)homes H/root/.hermes/venv/lib/python3.12/site-packages/hermes_cli/managed_uv.pymanaged_uv_pathrs9  DI%e|h&& %<$ ct}|jr/tj|tjr t |Sy)ubReturn the managed uv path if it exists, else ``None``. No side effects — pure lookup. N)ris_fileosaccessX_OKstr)ps r resolve_uvr+s2 Ayy{ryyBGG,1v rc8eZdZUdZded<ddfd ZdZxZS) _UvResultu``ensure_uv()`` return value that survives an update boundary. ``ensure_uv()``'s arity has flipped between a single path string and a ``(path, fresh_bootstrap)`` tuple across releases. ``hermes update`` runs the call site from the *old*, already-imported ``hermes_cli.main`` against this *freshly pulled* module, so the two can disagree on how many values ``ensure_uv()`` returns. An install parked on a 2-tuple release runs ``uv_bin, fresh_bootstrap = ensure_uv()`` against the single-value module and crashes the first update: the returned path is a plain ``str``, which is itself iterable, so the 2-target unpack walks its characters and raises ``ValueError: too many values to unpack (expected 2)`` (and on the failure path the ``None`` return raises ``TypeError: cannot unpack non-iterable NoneType``). This wrapper answers to both conventions: uv_bin = ensure_uv() # behaves as the path str ("" when absent) uv_bin, fresh = ensure_uv() # unpacks as (path|None, fresh_bootstrap) Missing uv is the empty string (falsy) instead of ``None`` so legacy 2-target call sites can still unpack a failure without raising, while ``if not uv_bin`` keeps working for single-value callers. POSIX only. This wrapper is **never** returned on Windows — see ``ensure_uv()`` for why the ``__iter__`` override is unsafe there. boolfresh_bootstrapc>t|||xsd}||_|S)N)super__new__r)clspathfreshself __class__s rr z_UvResult.__new__Rs$wsDJB/$ rcJtt|xsd|jfSN)iterrr)r$s r__iter__z_UvResult.__iter__Ws#c$i'4$*>*>?@@r)F)r" Optional[str]r#rreturnz '_UvResult')__name__ __module__ __qualname____doc____annotations__r r) __classcell__)r%s@rrr6s2 Arrct}|r|St}|jjddt d|jd t |t}|rDtj|dgddd jj}t d |d |St d |S#t $r.}tjd|t d|Yd}~yd}~wwxYw)zQResolve the managed uv path, installing it if necessary (plain ``str``/``None``).T)parentsexist_oku! → Installing managed uv into z ...zManaged uv install failed: %su$ ✗ Failed to install managed uv: N --versionFcapture_outputtextchecku ✓ Managed uv installed ()uA ✗ Managed uv install appeared to succeed but binary not found) rrparentmkdirprint _install_uv Exceptionloggerwarning subprocessrunstdoutstrip)existingtargetexcresultversions r_ensure_uv_pathrK^s|H  F MMt4 -fmm_D ABF\F .. [ !  &  ,WIQ78 M QR M# 6< 4SE:;s B88 C/$C**C/c^t}tjdk(r|St|S)uReturn the managed uv path, installing it first if necessary. On **POSIX** the result is a :class:`_UvResult` (a ``str`` subclass) that is both usable directly as the path *and* unpackable as ``(path, fresh_bootstrap)`` for older call sites parked on a 2-tuple release — see :class:`_UvResult` for the update-boundary rationale. On **Windows** we deliberately return a plain ``str``/``None`` instead. ``subprocess`` there serializes the argv via ``subprocess.list2cmdline``, which iterates every entry *as a string* (``for c in arg``). The dependency installer passes uv straight into the command list (``[uv_bin, "pip", ...]``), so a ``_UvResult`` — whose ``__iter__`` yields ``(path, fresh_bootstrap)`` rather than characters — would inject the bool into the command line and crash the install with ``TypeError: sequence item 1: expected str instance, bool found``. A plain ``str`` matches the historical Windows contract and is subprocess-safe. (A single value cannot satisfy both 2-target unpacking and Windows char-iteration: both use the iterator protocol, with contradictory results.) On failure the result is falsy — never raises — so callers can fall back to pip gracefully. r)rKr r r)rIs r ensure_uvrMs-. FI% V rcTt}|sytj|ddgddd}|jdk(rDtj|dgdddjj }t d |d |Stjd |j|j|S) uRun ``uv self update`` on the managed uv binary. Call this during ``hermes update`` so the managed copy stays current. Returns the managed path on success, ``None`` if uv isn't available or the self-update fails (non-fatal — the old version still works). Nr$updateTFr6rr5u ✓ Managed uv updated (r:z!uv self update failed (rc=%d): %s) rrBrC returncoderDrEr=r@debugstderr)rFrIrJs rupdate_managed_uvrSs|H  ^^ 68$  F A.. { #  &  *7)156 O  8&:K:KV]][ Orctj}itjt |j t |j d}|dk(r t |yt|y)aBootstrap uv into *target* using the official standalone installer. Uses ``UV_UNMANAGED_INSTALL`` (POSIX) or ``UV_INSTALL_DIR`` (Windows) so the astral installer writes the binary directly into ``$HERMES_HOME/bin/`` instead of ``~/.local/bin/``. )UV_UNMANAGED_INSTALLUV_INSTALL_DIRrN)r r renvironrr;_install_uv_windows_install_uv_posix)rGr envs rr>r>s\__ F  **  !$FMM 2fmm,  CC #rctjdd5}|j}ddd tjddddgd d tjd |g|d d  t j |y#1swYYxYw#t$rYywxYw# t j w#t$rYwwxYwxYw) zHDownload + sh the POSIX installer (two-stage to avoid curl|sh pitfalls).z.shF)suffixdeleteNcurlz-LsSfzhttps://astral.sh/uv/install.shz-oT)r9r7shrZr9r7)tempfileNamedTemporaryFilenamerBrCrunlinkOSError)rZfinstaller_paths rrYrYs  $ $E% @ A  W?~ V  > "    IIn %#  $     IIn %   sL A=8B'B =B BBB?B0/B?0 B<9B?;B<<B?cDd}tjdddd|g|ddy) z Invoke the PowerShell installer.z*irm https://astral.sh/uv/install.ps1 | iex powershellz-ExecutionPolicyBypassz-cTr`N)rBrC)rZcmds rrXrXs2 5NN )8T3?  rcyr')uv_binvenv_dirpython_versions r rebuild_venvrqsr)r+r)r+r*)rGrr+None)rZzdict[str, str]r+rr)z3.11)rnrrorrprr+r)r/ __future__rloggingrr shutilrBrapathlibrtypingrhermes_constantsr getLoggerr,r@rrrrrKrMrSr>rYrXrqrmrrrzsz#  ,   8 $ %A%APB>H.0  r