This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author uranusjr
Recipients asvetlov, rhettinger, uranusjr, yselivanov
Date 2022-02-10.09:23:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1644484997.64.0.607393944456.issue46622@roundup.psfhosted.org>
In-reply-to
Content
> should not use asyncio directly but 'async def', 'await', and `inspect.iscoroutine()` / `inspect.iscoroutinefunction()` instead.

Hmm, this introduces some difficulties. Since a coroutine can only be awaited once, a new coroutine needs to be returned (that simply return the result when awaited) each time __get__ is called. But this means we need a way to somehow get the result in __get__. If there’s a separate `cached_property_async` it’s possible to make __get__ a coroutine function, but personally I’d prefer the interface to match the PyPI cached_property.
History
Date User Action Args
2022-02-10 09:23:17uranusjrsetrecipients: + uranusjr, rhettinger, asvetlov, yselivanov
2022-02-10 09:23:17uranusjrsetmessageid: <1644484997.64.0.607393944456.issue46622@roundup.psfhosted.org>
2022-02-10 09:23:17uranusjrlinkissue46622 messages
2022-02-10 09:23:17uranusjrcreate