Wheel-next: Implementing pep proposals for an architecture aware pip

[aterrel]

Wheel-next is the github org that created to collaborate on POC’s for the various PEPs in flight. Often the first criticism of the PEPs is that it will add too much complexity to maintain, this complaint is most adeptly handled with a straight-forward simple implementation. Our hope is this is a place that is openly developed, but not strictly “owned” by any single entity.

A few things we are hoping to do here is make sure that anything we commit will be acceptable by the upstream Python projects. This means we have to pay attention to licenses, CLA requirements, and individual project styles. To that end the organization has several forked repositories that we are planning to build cuda-aware tooling, e.g. peps, scikit-build-core, warehouse.

The first thing to look at is the wheel-stub repository. This is the open version of the code being used to publish wheels that are larger than the limits of pypi.org. Effectively, a team can generate a stub sdist tarball that points to an external index for downloading the binary wheel.

Next is various prototypes for threads in the discuss.python.org board. (metadata-provider-nvidia, impl-package-metadata-index-json, metadata-provider-interface, impl-solve-for-variants) Each one has links to the various discussions and are very much in a state of early prototyping.