Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Uv-pack – Pack a uv environment for later portable (offline) install

github.com

Post reply on HN
Print view View original

1–5 of 5 posts

Show HN: Uv-pack – Pack a uv environment for later portable (offline) install

#1

Post by davnn »

I kept running into the same problem: modern Python tooling, but deployments to air-gapped systems are a pain. Even with uv, moving a fully locked environment into a network-isolated machine was no fun.

uv-pack should make this task less frustrating. It bundles a locked uv environment into a single directory that installs fully offline—dependencies, local packages, and optionally a portable Python interpreter. Copy it over, run one script, and you get the exact same environment every time.

Just released, would love some feedback!

Show HN: Uv-pack – Pack a uv environment for later portable (offline) install
github.com

Re: Show HN: Uv-pack – Pack a uv environment for later portable (offline) install

#2

Post by zahlman »

Just for the record, "uv environments" are ordinary Python virtual environments, and aside from the "optional portable Python interpreter" they are already contained within a single top-level directory. If just copying that folder wasn't working for you, that's because of absolute paths (in shebangs added to wrapper scripts, in the activation script, and maybe in `pyvenv.cfg` or something like that). Your approach avoids that by giving uv the data required to re-create the environment at the destination. (There have been many tools like this in the past and there's nothing fundamentally wrong with the idea.)

Re: Show HN: Uv-pack – Pack a uv environment for later portable (offline) install

#3

Post by davnn »

zahlman wrote: post #2

Just for the record, "uv environments" are ordinary Python virtual environments, and aside from the "optional portable Python interpreter" they are already contained within a single top-level directory. If just copying that folder wasn't working for you, that's because of absolute paths (in shebangs added to wrapper scripts, in the activation script, and maybe in `pyvenv.cfg` or something like that). Your approach av…

I would say uv provides quite a lot of additional features that can be used in various ways to create plain-old venvs. Note, however that uv-pack can also pack a subset of your uv-monorepo for a specific package (there are still some quirks I have to admit..).

My experience was that it‘s surprisingly painful to „just copy“ a venv and especially a uv-created venv. There are a lot of paths to be modified to get the venv working. Copying a venv felt hacky and wrong, that‘s why I built the tool :)

Re: Show HN: Uv-pack – Pack a uv environment for later portable (offline) install

#4

Post by zahlman »

davnn wrote: post #3
zahlman wrote: post #2

Just for the record, "uv environments" are ordinary Python virtual environments, and aside from the "optional portable Python interpreter" they are already contained within a single top-level directory. If just copying that folder wasn't working for you, that's because of absolute paths (in shebangs added to wrapper scripts, in the activation script, and maybe in `pyvenv.cfg` or something like that). Your approach av…

I would say uv provides quite a lot of additional features that can be used in various ways to create plain-old venvs. Note, however that uv-pack can also pack a subset of your uv-monorepo for a specific package (there are still some quirks I have to admit..). My experience was that it‘s surprisingly painful to „just copy“ a venv and especially a uv-created venv. There are a lot of paths to be modified to get the ven…

For what it's worth, the tooling I'm working (supposedly) on has a design intent of relocatable venvs.

Re: Show HN: Uv-pack – Pack a uv environment for later portable (offline) install

#5

Post by davnn »

zahlman wrote: post #4
davnn wrote: post #3

Earlier quoted context omitted.

I would say uv provides quite a lot of additional features that can be used in various ways to create plain-old venvs. Note, however that uv-pack can also pack a subset of your uv-monorepo for a specific package (there are still some quirks I have to admit..). My experience was that it‘s surprisingly painful to „just copy“ a venv and especially a uv-created venv. There are a lot of paths to be modified to get the ven…

For what it's worth, the tooling I'm working (supposedly) on has a design intent of relocatable venvs.

Do you have a link to share? Would be highly interested!
Post reply on HN