Well, the issues for torchvision and torchtext seem different. A  cpu-only package of torchvision should rely on a cpu-only package of pytorch so that’s really a bug, which we are fixing right now. But for torchtext, it is noarch package so we cannot pin the requirement to any version that user desire unless it adopts the same version specifier as pytorch and torchvision.