pydoctor: @type or Pythons type annotations?
![](https://secure.gravatar.com/avatar/148a51ecc80531586e1f5530d64b988a.jpg?s=120&d=mm&r=g)
Hello, I assume this is again a more religious question but I would be glad to hear your opinions and experiences about it. Let's assume we are using Python 3.9 or higher and epytext as documentation format with pydocotor. Whould recommand to use type-annotations or @type to give type informations to the pydoctor generated documentation?
![](https://secure.gravatar.com/avatar/bcb6ef473ff1644fddee1b4e7c730b01.jpg?s=120&d=mm&r=g)
On Sun, May 8, 2022, at 6:15 AM, c.buhtz@posteo.jp wrote:
We are generally moving toward type annotations in Twisted. They are superior to @type because they can be automatically checked for correctness, e.g. by Mypy. I'd recommend use of type annotation syntax in all cases it can express, reserving @type for exceptional circumstances. ---Tom
![](https://secure.gravatar.com/avatar/bcb6ef473ff1644fddee1b4e7c730b01.jpg?s=120&d=mm&r=g)
On Sun, May 8, 2022, at 6:15 AM, c.buhtz@posteo.jp wrote:
We are generally moving toward type annotations in Twisted. They are superior to @type because they can be automatically checked for correctness, e.g. by Mypy. I'd recommend use of type annotation syntax in all cases it can express, reserving @type for exceptional circumstances. ---Tom
participants (2)
-
c.buhtz@posteo.jp
-
Tom Most