The issue is that we cannot enforce order in a requirements.txt file and since PyTorch released a version 1.3.1 very recently, we were fetching a bigger file from pypi instead of the 1.3.0 cpu only hosted wheels (this was being fetched as a dependency of pyro-ppl). We could have fixed that by updating the torch dependency in requirements.txt to 1.3.1, but this would be a recurring issue with each update to pytorch.
Instead, the current workaround splits the installs into 2 requirement files - pytorch install + remaining, which should be more stable.
null-a
commented
4 years ago
Additionally, attempts to fix #70.
The issue is that we cannot enforce order in a
requirements.txtfile and since PyTorch released a version1.3.1very recently, we were fetching a bigger file from pypi instead of the1.3.0cpu only hosted wheels (this was being fetched as a dependency ofpyro-ppl). We could have fixed that by updating the torch dependency inrequirements.txtto1.3.1, but this would be a recurring issue with each update to pytorch.Instead, the current workaround splits the installs into 2 requirement files - pytorch install + remaining, which should be more stable.
build