Got it, thanks for the clarifications!
Tracking 3.x Python versions is fine. We already need to do that to support
things like new bytecodes, and PyTorch supports an explicit list of 3.x Python
versions with separate builds for each.
Tracking 3.x.y Python versions would be much more painful, a
The PyTorch team plans to use PEP 523 as a part of PyTorch 2.0, so this
proposal may break the next major release of PyTorch.
The related project is TorchDynamo, which can be found here:
https://github.com/facebookresearch/torchdynamo
We will likely move this into the core of PyTorch closer to r
