albedo
small gleam coding and persistent agent daemon with a detachable cli and a canvas ui albedo.sh
Star 115
Fork 23
Watch

Python remote is dependent on remote python #18

Open aly.codes
Open opened by aly.codes

This is a pretty big smell I'm workshopping solutions for. Right now the practical effect is:

  • remotes must have a compatible python installed
  • we are 3-4 major versions behind on python throughut the codebase
  • we nor agents can take advantage of more robust python libraries, e.g. pydantic or httpx.
  • tools can't take advantage of cython for speed

need to decide:

  • extent of support (darwin, linux, yes, but which architectures? how does nix work? how about windows/wsl?)
  • distribution mechanism (perhaps it should not be bundled with the app)
ptr.pet

i want this but also i dont really want to have 3 python versions and distribute that personally, so its ok if it was a build flag then i can disable it and manage the python myself (i say 3 bcz like, linux arm / x86 and mac arm. maybe everything else could just be downloaded)

okami.mom

the daemon already has machinery to push tars around over ssh so it can be possible for the daemon to download/cache an artifact and send it to a remote. i think we could have a managed way of albedo supplying a set python and its dependencies with user overrides? albedo should launch its kernel and helpers using an absolute interpreter path at least instead of supplanting the installed py.

prime agent installs 3.11 with uv with a venv in ~/.prime/agent/kernel-venv, i dont think its too crazy to do something similar though but i have a lot of trauma with python breaking on my machines because of having multiple versions so

okami.mom

i guess a lot of the headache can be gone by relying on UV to do the distribution

Sign up or Sign in to add to the discussion.