If no one is willing to take the time to send them a PR then the situation is simply not going to change until the project maintainers have both the time and inclination to add async/await markup support to Sphinx, and if they personally aren't doing any async coding then that won't change anytime soon.

Probably the best way forward is to reach consensus on the appropriate issue on how the solution should look in a PR they would accept, and then create the PR. But as project maintainer myself I'm not about to hold it against them for having not taken care of this.

On Tue, 4 Jul 2017 at 01:57 Alex Grönholm <alex.gronholm@nextday.fi> wrote:
I'm somewhat reluctant to send them any PRs anymore since I sent them a
couple of one liner fixes (with tests) which took around 5 months to get
merged in spite of me repeatedly reminding them on the Google group.

Nathaniel Smith kirjoitti 04.07.2017 klo 10:55:
> On Mon, Jul 3, 2017 at 11:49 PM, Alex Grönholm <alex.gronholm@nextday.fi> wrote:
>> The real question is: why doesn't vanilla Sphinx have any kind of support
>> for async functions which have been part of the language for quite a while?
> Because no-one's sent them a PR, I assume. They're pretty swamped AFAICT.
> One of the maintainers has at least expressed interest in integrating
> something like sphinxcontrib-trio if someone does the work:
> https://github.com/sphinx-doc/sphinx/issues/3743
> -n

Async-sig mailing list
Code of Conduct: https://www.python.org/psf/codeofconduct/