߲j dZddlZddlZddlZddlZddlmZddlmZejdk(Z ejdZ dZ ded ed efd Zd ed eded eedffdZded edzfdZded eefdZded dfdZded dfdZy)u+Hermes-owned PYTHONPATH stripping for child processes. Launchers prepend the repo root and the Hermes venv's site-packages so the backend can ``import tools``; leaked into a child Python of a DIFFERENT version they load the backend's C extensions and crash. Only entries proven Hermes-owned by *path provenance* are removed — never by a cross-version heuristic. Module state (``_hermes_repo_root_aliases``, ``_in_venv``, ``_hermes_site_packages``) lives in ``tools.environments.local`` (via :func:`_state`) so tests monkeypatching it there keep working.NPath)_ACTIVE_VENV_MARKER_VARSWindowsztools.environments.localcddlm}|S)zEReturn the ``tools.environments.local`` module (owner of the caches).rlocal)tools.environmentsr rs H/home/ubuntu/.hermes/hermes-agent/tools/environments/local_pythonpath.py_stater s ( Lleftrightreturnc|jDcgc]!}tjj|#c}|jDcgc]!}tjj|#c}k(Scc}wcc}w)z;Compare path spellings with host filesystem case semantics.)partsospathnormcase)rrps r _same_pathrsS)- 4ABGG  Q  4V[VaVa8bQR9I9I!9L8b bb 48bs &A0&A5 resolved_root lexical_rootconfigured_home.c  ||g}|g}|jjdk(r%|j|jj|D]} |j}tj j t|}tj j|tj j t|g|k(rD|j|tj jt|t|z |D]H}||jz } |jd|jdk(r|j|Jg} |D]( t fd| Dr| j *t| S#ttf$rYewxYw#t$rYwxYw)aExact repo-root spellings emitted by Hermes launchers. Mirrors ``gateway_windows._preserve_hermes_home_path`` (physical path under the resolved HERMES_HOME -> configured spelling) so a junction-backed install matches without treating arbitrary HERMES_HOME descendants as Hermes-owned. A repo-level junction (possibly cross-drive) is accepted only when a strict resolve proves / is the physical root (fail-closed).profilesT)strictc36K|]}t|ywNr).0existing candidates r z2_build_hermes_repo_root_aliases..DsKx:i2K)parentnameappendresolverrrstr commonpathrelpathOSError ValueErroranytuple) rrr candidateshome_candidateshome resolved_homehome_keyrepo_candidatealiasesr#s @r _build_hermes_repo_root_aliasesr8"s .J''O""j055<<=  LLNMww''M(:;Hww!!8RWW-=-=c->P-Q"RSW__!!$]9KSQ^M_)`"`a   2 22 %%T%2m6K6KSW6K6XX!!.1 G& K7KK NN9 %& >$      s% CF*6F2F/.F/2 F>=F>envct|jdxsd|jdr&tfdtjDsy dz j rSdS#t $rYywxYw)zProducer-owned runtime venv identified by VIRTUAL_ENV, or None. The variable alone is not provenance (users carry unrelated venvs): require the legacy Windows base-Python producer's exact ``/venv`` layout AND a real ``pyvenv.cfg``. VIRTUAL_ENVc3<K|]}t|dz yw)venvNr )r!rootr#s r r$z*_validated_runtime_venv..Ns#-a59Jy$- 0-asNz pyvenv.cfg)rgetr/r _hermes_repo_root_aliasesis_filer-)r9r#s @r _validated_runtime_venvrCIs}SWW]+1r2I 77= !-a=CX=_=_-a*a&5>>@yJdJ sA0.A00 A<;A<ct}|jg}|jr ddl}|j d|j D|sdtjddtjd}|jtrttjdz dz n!ttjd z |z dz t||_t|j}t|}|-|dz dz tfd |Ds|j|S#t $rYwxYw) zExact site-packages dirs owned by the Hermes runtime (cached): ``site.getsitepackages()`` with a ``sys.prefix`` fallback, plus a validated Windows base-interpreter launch's ``VIRTUAL_ENV/Lib/site-packages``.Nrc32K|]}t|ywrr)r!sps r r$z,_get_hermes_site_packages..asH2d2hHspython.Libz site-packageslibc36K|]}t|ywrr )r!r"runtime_site_packagess r r$z,_get_hermes_site_packages..nsV8:3X>Vr%)r _hermes_site_packages_in_venvsiteextendgetsitepackages Exceptionsys version_infor( _IS_WINDOWSrprefixlistrCr/)r9r resultrPpyver runtime_venvrMs @r _get_hermes_site_packagesr\Ws% HE ""* >>  H1E1E1GHH !1!1!!4 5Qs7G7G7J6KL Kd3::.6H#' #3e#;e#Co#UW&*6l# %-- .F*3/L ,u 4 FVvVV MM/ 0 M  s*D44 E?EcTt|tD]}|j|dy)zStrip Hermes-owned PYTHONPATH entries, then the runtime marker vars. Order is load-bearing: PYTHONPATH filtering runs BEFORE the markers go so a validated Windows base-interpreter launch (VIRTUAL_ENV -> /venv) can still prove ownership.N)_strip_hermes_owned_pythonpathrpop)r9_markers r 2_strip_hermes_owned_pythonpath_and_runtime_markersrass)#3'+ r c|jd}|sygt|tj}|j t j }|Dcgc]stfd|Ds}}|Dcgc] }||vs| }}|r#t j j||d<n|jdd|rtjd|yycc}wcc}w)uRemove Hermes-owned PYTHONPATH entries: only exact matches of the repo root (any launcher spelling) and runtime site-packages — never descendants, which are user paths. Empty components (= cwd) and everything else are preserved. Everything else -- user libs, Nix plugin paths, a pythonX.Y/site-packages entry meant for a DIFFERENT child version -- is preserved byte-for-byte: ownership is decided by path provenance, never by a cross-version heuristic (#74817 follow-up). PYTHONPATHNc3HK|]}tt|ywr)rr)r!res r r$z1_strip_hermes_owned_pythonpath..s/\1 47A0F/\s"z1Stripped Hermes-owned entries from PYTHONPATH: %s) r@r\r rAsplitrpathsepr/joinr_loggerdebug)r9pp owned_pathsentriesrestrippedkepts ` r r^r^|s  B X-c2XVX5W5WXKhhrzz"G"]aaC/\P[/\,\]H] 4!!8"3A 4D 4 JJOOD1L  d# H(S ^ 4sC##C#8C# C( C()__doc__loggingrplatformrTpathlibr#tools.environments.local_env_policyrsystemrV getLoggerrir boolrr0r8dictrCrXr\rar^r r rzs2  Hhoo9,   5 6cTc$c4c $$'+$>B$ 49$N  $+ 4DJ8DTTTTr