Replies: 1 comment
-
Seems like this is a PyTorch bug, which was fixed last November by pytorch/pytorch#89115. I recommend to anyone facing the same issues as me to upgrade their PyTorch version. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I face the problem that docstrings generated by pybind11 for functions with PyTorch
at::Tensor
objects haveat::Tensor
in the Python interface instead oftorch.Tensor
, e.g.:I saw that the docs were mentioning this type of problem (https://pybind11.readthedocs.io/en/stable/advanced/misc.html#avoiding-c-types-in-docstrings).
I tried the following workaround, but to no avail (
at::Tensor
still remains in the docstring).Am I using pybind11 incorrectly or is this actually a bug?
Here's the corresponding Python code:
Beta Was this translation helpful? Give feedback.
All reactions