On Thu, Feb 12, 2015 at 2:35 PM, Ben Darnell <b...@bendarnell.com> wrote: > But then the coroutine object has a return type as well, which needs to be > represented somehow. I think it's better to let the "return type" portion of > the docs represent the eventual return value of the coroutine. The coroutine > aspect of the function is most analogous to staticmethods and classmethods, > which are given a special prefix in the docs: > https://docs.python.org/3/library/stdtypes.html?highlight=fromkeys#dict.fromkeys > > Unfortunately it looks like these are built into sphinx so it's not as easy > to add a new one (unless I'm missing something), but this seems like a good > addition for the next version of sphinx.
You are right, Ben, the best solution seems to be a sphinx extension to generate markup like those classmethod tags. Cheers, Luciano -- Luciano Ramalho Twitter: @ramalhoorg Professor em: http://python.pro.br Twitter: @pythonprobr
