# PEP 759, External Wheel Hosting **URL:** \ **Category:** Standards\ **Created:** [October 3, 2024, 1:12am UTC](https://discuss.python.org/t/pep-759-external-wheel-hosting/66458 "2024-10-03T01:12:24Z")\ **Posts on this page:** 1\ **Showing post:** 46
**Author:** ![atalman](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/atalman/32/23037_2.png) [@atalman](https://discuss.python.org/u/atalman)\ **Post date:** [October 18, 2024, 1:41pm UTC](https://discuss.python.org/t/pep-759-external-wheel-hosting/66458/46 "2024-10-18T13:41:10Z")
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](http://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 : 1. 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 ? 1. We are currently migrating our current CDN solution to Meta hosted CDN. Our PyPI Index is hosted in our regular [download.pytorch.org](http://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 --- _[View the full topic](https://discuss.python.org/t/pep-759-external-wheel-hosting/66458)._