pytorch

4ea6a3aa - Fix issues with printing certain torch modules (#62447)

Fix issues with printing certain torch modules (#62447) Summary: Fixes https://github.com/pytorch/pytorch/issues/54420 When I tested on master, with the testing code, there were multiple objects on the garbage collector that cannot be printed. Testing code: ``` import torch import gc import os import sys print(torch.__version__) a = torch.rand(10) print(a) objects = gc.get_objects() for i in range(len(objects)): print(objects[i]) ``` ### 1 ``` print(torch.classes) ``` Like SplitInfinity has mentioned in the GitHub issue, the solution here is to set `__file__` for `torch.classes` to something. Similar to [_ops.py](https://github.com/pytorch/pytorch/blob/master/torch/_ops.py#L69), where `__file__` is set to `_ops.py`, we could set `__file__` for torch.classes to `_classes.py`. ### 2 ``` print(torch._ops.ops.quantized) print(torch._ops.ops.atan) ``` When we try to print these two modules, it will call `_OpNamespace::__getattr__`, but the `op_name` is `__file__`. This becomes a problem when `torch._C._jit_get_operation(qualified_op_name)` [(link)](https://github.com/pytorch/pytorch/blob/master/torch/_ops.py#L60) tries to look for an actual op on the native C++ side. Only when we get the attribute for an actual op, e.g. `print(torch._ops.ops.quantized.elu)`, the `op_name` becomes proper (e.g. `elu`). My current solution is to return a hardcoded string (i.e. “torch.ops”) if `op_name` is `"__file__"`. Pull Request resolved: https://github.com/pytorch/pytorch/pull/62447 Reviewed By: saketh-are Differential Revision: D30234654 Pulled By: yidawang-oss fbshipit-source-id: de43a8f599739c749fb3307eea015cc61f1da60e