I have recently learned of the deprecation and pending removal of asyncio.coroutine (deprecated since 3.8, to be removed in 3.10), and this will greatly affect a pattern of using it to safely wrap regular functions when executing them in an async context.
This pattern is very helpful when writing libraries and frameworks, where end users can submit their own callables to be executed by the library code (e.g. callbacks and similar); allowing the users to submit both coroutines and regular functions greatly helps with their learning curve.
Of course, this can be replaced by a simple asyncio.iscoroutine check, but it is practical to have a simple decorator that can be used inline (including on lambdas).
Is there any chance that the decision to remove asyncio.coroutine could be reversed?