Currently one test fails for torch < 1.11 because torch.complex128 support was only added in 1.11.
Torch 2.0 seems good across the board. I recommend changing torch requirement at least to torch>=1.8.1, allowing usage in Torch 2.0.
I think we still want to support 1.8.1 given it is only a single test failing at the moment.
atong01
commented
1 year ago
Currently torchdyn claims requires
torch<2.0.0,>=1.8.1. This issue tracks version compatibility. Github action testing against OS, python version and torch version can be found here: https://github.com/atong01/torchdyn/actions/runs/5939235577/job/16105229599Currently one test fails for torch < 1.11 because
torch.complex128support was only added in 1.11. Torch 2.0 seems good across the board. I recommend changing torch requirement at least totorch>=1.8.1, allowing usage in Torch 2.0.I think we still want to support 1.8.1 given it is only a single test failing at the moment.