Skip to content

Explore alternative storage options for wheels #11

@urob

Description

@urob

The current approach of storing binary wheels in the wheelhouse branch and deploying them alongside the index is pushing the boundaries of Github's storage and deployment limits.

A couple of options:

  1. Separate the index from the wheelhouse branch. This solves the more pressing 1GB deployment limit. But it still inflates the repository, which is subject to a soft 5GB limits.

  2. Deploy wheels as release artifacts and link them from index. There is no official information about permanence but it seems that other repositories are able to store release artifacts indefinitely.

  3. Push them to PyPI with a custom suffix to avoid name conflicts, then link from the index. The downside of this is that the PyPI name wouldn't match the package name, which would be confusing for people trying to install directly from the PyPI index.

  4. Push them to anaconda.org/urob. This resolves the deployment limit but is subject to a 3GB storage limit.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions