Samuel Colvin

I've changed my mind, @lilyminium you PR looks great, needs some fixes, but I'd be happy to accept it for v1.10.

Correct, sorry for confusion. See #4456 for discussion of strategies in v2.

I disagree, documenting everything would be extremely difficult. In the end, the only real source of truth is the code itself. One of the reasons we're all writing python not...

See [this](https://github.com/aio-libs/aiohttp/issues/4078) fairly long discussion on the matter. I'm strongly opposed to multiple different types of documentation, I think there should be one and only one section of documentation on...

Thanks for your input, I get where you're coming from. Let's see what others think, if lots of people support this I'll think about it more. Requirements: * follows the...

There [is documentation on field arguments](https://pydantic-docs.helpmanual.io/usage/schema/#field-customisation).

I have plans for this. It it won't be using sphinx, but rather mkdocstrings which I've used very successfully recently in dirty-equals and watchfiles.

Mkdocstrings can do the same thing I think.

Interesting question, @pawamoy would there be a way for others to reference pydantics docs from their docs?

It does: https://pydantic-docs.helpmanual.io/usage/schema/#field-customization API documentation will be done in V2, this is already stated in the blog about V2.