Allow coroutines on add_listener.

The current code that process a notification uses the method call_soon which expects a callable, why not to use create_task (or ensure_future for compatibility reasons) after checking if the callback is a coroutine?

There are different ways to do this, either just checking if the callback is a coroutine as described in here for example. Another way is just to add an extra argument or a different method to register coroutines.

Would it make sense to add a context? I am currently passing extra arguments to the callback via functools.partial.

Let me know if something like this would be accepted I can create a PR with the implementation.

Commencer par le point d’entrée add_listener et le traitement des notifications qui appelle actuellement call_soon. Comparer create_task et ensure_future pour les callbacks de coroutine, notamment l’utilisation existante de functools.partial pour les arguments supplémentaires. Done doit inclure une API de callbacks convenue et un comportement de compatibilité, avec des tests couvrant les listeners classiques et de coroutine.