Closed general

adom-google DOA in fresh workspace — missing Python 'requests' dep, image blocks all obvious fixes

Drew Owens · 1mo ago ·closed by John Lauer
hd-feedback

Type: Bug · [hd-feedback]

adom-google installs but is dead on arrival in a fresh Hydrogen Desktop workspace — it crashes on every invocation because its Python requests dependency is missing from the workspace image, and the image's Python environment blocks the obvious fixes.

Symptom

Any adom-google command immediately aborts:

$ adom-google --version
Traceback (most recent call last):
  File "/home/adom/.local/bin/adom-google", line 25, in <module>
    import requests
ModuleNotFoundError: No module named 'requests'

Root cause

  • /home/adom/.local/bin/adom-google is a #!/usr/bin/env python3 script that does a top-level import requests.
  • The workspace image's system Python (/usr/bin/python3, 3.12.3) has no requests and the package ships no vendored deps / venv / pipx env.
  • Reinstalling via adom-wiki pkg install adom-google does not help — it only copies the bin + skills, never provisions Python deps.
  • The environment then blocks the two obvious repairs:
    • apt-get install -y python3-requestsE: Unable to locate package python3-requests
    • pip install --user requests → PEP 668 externally-managed-environment refusal.

Workaround (what unblocked me)

python3 -m pip install --user --break-system-packages requests

requests 2.34.2 installed and adom-google status then ran fine. But --break-system-packages is not something a fresh user should have to discover, and it dirties the system Python.

Environment / versions

item value
adom-google 0.7.0 (published 2026-06-30)
adom-google-adom (provider) 0.4.1
adom-wiki CLI 1.0.8
OS Ubuntu 24.04.4 LTS
Python 3.12.3 (/usr/bin/python3, PEP 668 externally-managed)
HD Windows / WSL2 workspace

Repro

  1. Fresh workspace, no prior adom-google.
  2. adom-wiki pkg install adom-google
  3. adom-google --versionModuleNotFoundError: No module named 'requests'.

Suggested fixes (any one)

  • Package adom-google with its own venv / pipx install (like other Python tools), or vendor requests/switch to stdlib urllib so it has zero third-party deps.
  • Or bake python3-requests (and friends) into the Hydrogen Workspace image so the system Python satisfies it.
  • Or have adom-wiki pkg install run a declared post-install dependency step for Python packages.

Filed by hand via adom-wiki discussion ([email protected]). Happy to test a fix.

1 Reply

John Lauer · 10d ago

The image-level blocker is resolved. Verified live on the current golden image (v21): python3 'import requests' -> requests OK 2.31.0. The 'requests' dependency ships in the image now, so the DOA-on-fresh-workspace failure this issue reports no longer occurs. (The adom-google CLI itself is a Tier-B on-demand install, not on PATH by default — separate from the missing-dep blocker reported here.) Closing the blocker; reopen if adom-google still fails to install on a >= v21 image.

Log in to reply.