Cairn

google-workspace setup.py import and dependency issues

NousResearch/hermes-agent · cluster 12722 · apps/desktop

Data as of

5 open items. Fix attempted, not merged.

The short answer

3open issues
2open PRs
8items grouped
Known?
Yes. 8 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
3 issues and 2 PRs.

These items concern failures in the google-workspace skill's setup.py related to unavailable hermes_constants imports, missing Google API dependencies, and Python version compatibility problems including PEP 604 union syntax on Python 3.9.

Open issues3

  • Issue#14688google-workspace setup.py crashes under macOS system python3 (auto-reexec into venv)
  • Issue#39536Desktop app crashes on macOS: findSystemPython() picks Python 3.9 from /usr/bin, fails on str | None syntax
  • Issue#43913[Bug]: Desktop install loop on macOS — launcher uses system python3 (3.9) instead of bundled venv, hermes_cli import fails, gateway never starts

Open PRs2

  • PR#39585fix(desktop): prefer supported POSIX Python
  • PR#77638fix(desktop): probe-gate and version-order the POSIX Python fallback

2 PRs closed without merging

From the close comments: closed without comment 1 · merged via another change 1

  • #12729 fix(skills): google-workspace setup.py fallback when hermes_constants unavailable · closed without comment
  • #15158 fix(google-workspace): defer PEP 604 unions so setup.py runs on Py3.9 (#14688) · merged via another change → #13038
Closed issues · 1
  • Closed#12722[Bug]: google-workspace skill setup.py fails — hermes_constants import + missing Google API deps
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.18: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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 Lab

At a glance

Subsystem
apps/desktop
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/12722.json
cluster/12722.md