Mike DePalatis

You're right about `on_finish`. The documentation describes it as a counterpart to `prepare` which may be awaitable. Maybe it would make sense to allow it to be asynchronous, too.

Rather than choosing a naming convention based on legacy code, what about renaming `include_host` and emit a deprecation warning when that gets used?

There is already a file upload demo [here](https://github.com/tornadoweb/tornado/tree/master/demos/file_upload). It is also mentioned [in passing in the documentation](https://www.tornadoweb.org/en/stable/httpclient.html#example-code), though I think it could be made more prominent (somewhere in the User's...

Using queues is definitely an option, but as you have described it can be tricky to synchronize between the sync and async versions (if you look at how Janus works,...

No, the API documentation located here does not actually contain API documentation: https://flask-caching.readthedocs.io/en/latest/api.html

Looks resolved to me as well.

> We do have some API documentation embedded throughout the docs. Eg. within the spoilers on [this page](https://connexion.readthedocs.io/en/latest/quickstart.html). Honestly I hadn't even noticed that. It may be a personal preference...

This seems like a question that is asked frequently enough that an example solution should be included in the user's guide section of the docs. I would consider adding something...

You are right that there are plenty of caveats to how to really do a graceful shutdown depending on the deployment strategy. But for the guide, maybe it would suffice...

It is actually documented in an example that you can add the following to placate type checkers: ```python Schema: ClassVar[Type[Schema]] = Schema # For the type checker ```