WARNING: error while formatting signature: Handler <function process_signature at 0x00000280E14DCC10> for event 'autodoc-process-signature' threw an exception
See original GitHub issueHello,
i’m currently trying to use sphinx-autodoc-typehints to create a nice documentation for my project pyage (https://github.com/Timtam/pyage). I do have an issue however. When i’m annotating a method like this:
def quit(self) -> None:
"""
This method will tell the game loop to quit as soon as possible, releasing all resources in the process.
Parameters
----------
Returns
-------
:obj:`None`
"""
sphinx-autodoc-typehints will fail with an indescriptive error when processing the signature of that method: WARNING: error while formatting signature for pyage.app.App.quit: Handler <function process_signature at 0x00000280E14DCC10> for event ‘autodoc-process-signature’ threw an exception (exception: ‘quit’)
I’ve configured my sphinx-autodoc-typehints as follows:
extensions = [
"sphinx.ext.autodoc",
"sphinx.ext.intersphinx",
"sphinx.ext.todo",
"sphinx.ext.viewcode",
"sphinx.ext.napoleon",
"sphinx_autodoc_typehints",
]
napoleon_use_param = True
Do you have any idea of what might cause this issue, or how I can help you digging deeper into the issue?
I’m running Python 3.8.2 with sphinx 3.3.1 and sphinx-autodoc-typehints 1.11.1. Thanks.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (2 by maintainers)
I think a PR from me side is out of scope. I’m not a Sphinx / Sphinx extension developer and I have no knowledge about this particular extension nor why a meta class should break the code or cause such a hard error.
In addition, I tried multiple time to debug Sphinx code, but it’s just a nightmare how it’s programmed and documented. It’s still a nice tools and it works, but fixing problems in Sphinx is a nightmare as it has no clear and documented software architecture.
Sorry.
If you like, I can try to make a minimal example and also try to narrow it down.
@gaborbernat I know this situation as I’m also involved in >40 projects - in many of them as maintainer 😃
Anyhow, I’ll provide a minimal reproducer for investigations. Since a while I have it on my todo list. I just accidently found this issues. Until a few days ago, I though I’m alone with this problem and it might be due to other extensions or special code I’m using. So with this open issue, I have a first idea how to narrow it down.