Reference to asyncio in synchronous method gmqtt.client.Client.publish about gmqtt

[Mixser]

@rkrell

Thanks for notice. As I can see, you are using threads (and pypy) and we didn't tested our lib in such way of usage.

May be the asyncio.set_event_loop method will be useful for you cases. I mean you need to connect the event loop to your threads before using the async methods in it.

If you did it and the problem still happening, notify us.

And thanks for your PR. 😊

[rkrell]

Thanks for merging, the above traceback does no longer occur now.

Would appreciate a release just in case of some spare time ;-) Thank you in advance

[rkrell]

The async_to_sync wrapper is just a workaround, because I need to call async methods from within the gmqtt callbacks. Best would be having coroutines as callbacks, that would simplify it a lot.

Thank you all for acting so fast.

[Mixser]

Hi,

We support an async callback only for on_message. May be it will help you.

Also you always can add coroutine to event loop from sync method in this way:

async def example(*args, **kwargs):
    # do async stuff
    pass

def on_message(*args, **kwargs):
    asyncio.ensure_future(example(*args, **kwargs)

[rkrell]

Aha, I see now:

gmqtt/gmqtt/mqtt/handler.py

Lines 296 to 299 in d198e5b

	if iscoroutinefunction(self.on_message):
	asyncio.ensure_future(self.on_message(self, print_topic, packet, qos, properties))
	else:
	self.on_message(self, print_topic, packet, qos, properties)

Very good solution, to be able to use sync and async according to the needs.
This will help much avoiding workarounds. Thanks.

[rkrell]

Also you always can add coroutine to event loop from sync method in this way:

async def example(*args, **kwargs):
    # do async stuff
    pass

def on_message(*args, **kwargs):
    asyncio.ensure_future(example(*args, **kwargs)

Good point, will try this.