NousResearch/hermes-agent
Store Python PATH isolation and PEP 668 marking
Cluster 129097 · environments. Data as of
2 open items. Fix attempted, not merged.
The short answer
1open issue
1open PR
3items grouped
- Known?
- Yes. 3 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 1 PR closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 1 PR.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese items address how the store-managed Python installation is exposed (or kept off) the terminal PATH, and how it is marked as externally managed per PEP 668 before publishing. The work touches both terminal resolution behavior and store entry integrity.
Open issues1
- Issue#129097terminal: `python`/`pip` resolve to Hermes's store Python, and `pip install` writes into a hash-verified store entry
Open PRs1
- PR#129151fix(pm): mark the store Python as externally managed before publish
1 PR closed without merging
From the close comments: closed without comment 1
- #129149 fix(terminal): keep store Python off terminal PATH; PEP 668 marker (#129097) · closed without comment
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- environments
- Closed issues
- 0
- Attempts
- 1 PR closed without merging