Hello. I am from PyTorch Dev Infra team.
I am fully supportive of this Proposal. I believe this can solve some of our current issues:
- PyTorch PyPI channel size constantly growing due to large wheel size of PyTorch binary. Currently around ~900MB for 2.5 release.
- Allow us to build better test/staging PyPI channel to test binaries before publishing to PyPI. Currently we use download.pytorch.org/whl/test to test our wheels.
- Potentially give us ability to host binaries with different CUDA versions on PyPI (Currently we only host CUDA 12.4 for Linux).
I have couple of questions :
- As Per this PEP: Organization accounts do not automatically gain the ability to externally host wheels; this feature MUST be explicitly enabled by PyPI admins at their discretion.
- Maybe we can elaborate a little bit more here, what will onboarding process be like ?
- We are currently migrating our current CDN solution to Meta hosted CDN. Our PyPI Index is hosted in our regular download.pytorch.org but wheels themselves will be hosted either on our current CDN solution or Meta CDN solution (via redirect to different URL). Hence we are planning to have 2 CDN solutions wending wheels. Will this use case be supported in this proposal ?
Thank you,
Andrey