Skip to content

Standalone executables #2

Description

@Tremeschin

As seen on the readme, fully offline binaries are planned.

This feature helps for full isolation of projects, ensuring upstream updates don't break it, and archiving, security purposes.

  • There's some technical problems to solve, for one bundling an exact python distribution uv would install. This can be done by running uv python install (version) on the bundle directory, but the host system must be able to run the target platform files 🫤

  • On internal R&D I bundled astral-sh/python-build-standalone successfully, but getting uv to use it in uv run was unstable.

  • Another point of failure is supporting downloading the appropriate PyTorch wheels for the platform and backend.

However, the biggest problem by far, is bundling all the dependencies wheels for one's project. There's an upstream effort and awareness for supporting uv pip wheel subcommand to export them, whenever it's feasible I'll implement it.

Also, uv pip install --help has --python-version and --python-platform, this will be interesting in a pip wheel command.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions