Not a week goes by without a new issue popping up. A dependency manager is a critical piece of infrastructure, it should not be the main developer experience bottleneck when building an application. A good package manager is out of sight, out of mind. You don't hear people complaining so much about Cargo every day.
I don't really feel like defending poetry, I don't even use it. But in this particular case, I think the wheel format and the way people try to host it on their servers and the entitled researchers who act like 80 year olds and "just want things done" instead of taking a little bit of time to learn to work with their tools are to blame. None of this exists with the cargo infra.
https://download.pytorch.org/whl/torch/
It's meant to be an automated process, don't make excuses for poor implementation on behalf of Poetry.
See for yourself the number of torch related issues:
https://github.com/python-poetry/poetry/issues?q=is%3Aissue+...
https://github.com/python-poetry/poetry/issues?q=is%3Aissue+...
Not a week goes by without a new issue popping up. A dependency manager is a critical piece of infrastructure, it should not be the main developer experience bottleneck when building an application. A good package manager is out of sight, out of mind. You don't hear people complaining so much about Cargo every day.