That doesn’t look like valid Python code to me, and it doesn’t mention Futures at all. Maybe it’s logging output? Could you quote the actual code instead?
Ah, I didn’t realize the : LOGGING_STATUS parts were type annotations.
Anyways, @pebl: Why do you want variables that are resolved futures, disconnected from any loop? How are these used? That DeprecationWarning isn’t going to be removed and will only get worse in the future, so the best thing to do is figure out what that code was trying to do and find a different way to express it.
instead of a Future (which you should basically never use directly - it’s only for low level code to translate between callbacks/protocols and tasks) use an Event wrapped with an awaitable class: