OSSForks/pytorch
1
0
Fork 0
mirror of https://github.com/zebrajr/pytorch.git synced 2025-12-06 12:20:52 +01:00
Code Issues Actions 38 Packages Projects Releases Wiki Activity

[FX][docs] minor fixes (#58085)

Browse Source 
Summary: Pull Request resolved: https://github.com/pytorch/pytorch/pull/58085

Reviewed By: mruberry

Differential Revision: D28364553

Pulled By: jamesr66a

fbshipit-source-id: 0d953672de9a86ecf5b1900b22e6ddef850dbe8f
This commit is contained in:
Gary Miguel 2021-05-11 15:34:39 -07:00 committed by Facebook GitHub Bot
parent a13718b69f
commit f9c8b7f1a8
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/source/fx.rst
View File

@ -52,7 +52,7 @@ run it. Ensuring that the inputs and outputs of your FX transform are a
import torch
import torch.fx
def transform(m : nn.Module) -> nn.Module):
def transform(m : nn.Module) -> nn.Module:
gm : torch.fx.GraphModule = torch.fx.symbolic_trace(m)
# Modify gm.graph
@ -831,9 +831,9 @@ FX uses ``__torch_function__`` as the mechanism by which it intercepts
calls (see the `technical
overview <https://github.com/pytorch/pytorch/blob/master/torch/fx/OVERVIEW.md#technical-details>`__
for more information about this). Some functions, such as builtin Python
functions or those in the ``math`` module, are things that are not
covered by ``__torch_function__``, but we would still like to capture
them in symbolic tracing. For example:
functions or those in the ``math`` module, are not covered by
``__torch_function__``, but we would still like to capture them in
symbolic tracing. For example:
::