Henry Tanner

I have created a repository with a fully working example and step by step instructions on how to reproduce the error. https://github.com/henryJack/sphinx_issue/blob/master/README.md The module in question is here https://github.com/henryJack/sphinx_issue/tree/master/mymodule. Yes,...

Good discussion here on how typing can lead to circular imports: https://github.com/python/typing/issues/105... The issue is that everything works up until the point you add the `sphinx-autodoc-typehints` extension to the conf.py...

It should be changed so that string type annotations should never get evaluated. Python runs this just fine... from typing import TYPE_CHECKING if TYPE_CHECKING: from mymodule.class_b import B class AClass:...

Circular imports for type checking are valid, they don't need to be fixed

Wouldn't it be better though if offending types are just ignored and displayed as strings and not links. Currently, it breaks the whole make docs process. It's a great library...

Ideally, A warning + unlinked string would be great. This other example would also break the sphinx build and is 100% valid python ```python class Assembly: def __init__(self) -> None:...

As far I can tell, the code for `sphinx-autodoc-typehints` is just one file, right (`sphinx_autodoc_typehints.py`)? If you could just highlight which areas I would need to look at to intercept...

+1 on that. Any word on whether this is still in progress?

@debnet, Yes, a limited number of POST requests will show up in DRF docs. For example, this URL allows GET and POST...  and both of them show up in...

For ModelViewSets the DRF docs does not display the "POST" option... The top two images show a valid POST, GET and OPTIONS request for a given URL. But the bottom...