tree 03d2533ef4bd9751a08070a79c8b53261bf2d5ee
parent 4809e838c1c8d6c38ab8c8cb987f243cc3bfcc1e
author Richard Zou <zou3519@gmail.com> 1670963766 -0800
committer PyTorch MergeBot <pytorchmergebot@users.noreply.github.com> 1671034857 +0000

Fix circular import in torch/autograd/function.py (#90415)

It turns out it is possible to break cycles by not directly importing a
module:
- there's a problem that torch.jit imports torch._ops and torch._ops
import torch.jit
- there's another problem that torch.autograd.function imports
custom_function_call but torch._functorch.autograd_function imports
torch.autograd.function

The "better" way to handle all of this is to do some large refactoring so
that torch._functorch.autograd_function imports some file that has
_SingleLevelAutogradFunction and then have torch.autograd.function
depend on torch.functorch.autograd_function... (and ditto for torch.jit
vs torch._ops), but I'm scared to move code around too much for BC
reasons and the fix in this PR works well.

Test Plan:
- import torch
Pull Request resolved: https://github.com/pytorch/pytorch/pull/90415
Approved by: https://github.com/albanD, https://github.com/soulitzer