PyTorch and the PyPI supply chain
PyTorch and the PyPI supply chain
Posted Jan 12, 2023 17:22 UTC (Thu) by kleptog (subscriber, #1183)In reply to: PyTorch and the PyPI supply chain by rgmoore
Parent article: PyTorch and the PyPI supply chain
For example, it would be possible for someone to write a bot that checked if the contents of the wheels distributed by PyPI match the source in the indicated repository. The problem is there is nowhere to place this information in a way that is of any use. Or, it would be nice to straight up reject any package that has existed for less than 3 months. Or being able to namespace dependencies to ensure they come from the right repository.
Python is here paying the decision early on that no packaging/repository standard would be made and to let the community create one organically. It's biting back hard now. More recent languages did not repeat that mistake.
PS. Don't talk to me about solutions like Nexus which try to solve the problem on the client-side but don't really have any extra information to work with and so just end up adding an extra layer of frustration. Until the necessary information is available in machine readable form no client-side tooling can help.
