Assert that there is no message to receive using ApplicationCommunicator

[django]

Assert that there is no message to receive using ApplicationCommunicator

[andrewgodwin]

Yes, we should probably have this - I won't be able to add it myself for a while though as I've got bugs to fix elsewhere. Feel free to submit a PR if you want.

[dgilge]

Ok, fine. What about the following? (I'm not sure about the sleep times yet. And I'd actually prefer to implement queue_empty simpler...)

    async def queue_empty(self, timeout=0.1):
        if not self.output_queue.empty():
            return False
        if timeout <= 0.01:
            await asyncio.sleep(timeout)
            return self.output_queue.empty()
        await asyncio.sleep(0.01)
        if not self.output_queue.empty():
            return False
        await asyncio.sleep(timeout - 0.01)
        return self.output_queue.empty()

    async def queue_count(self, wait=0.1):
        await asyncio.sleep(wait)
        return self.output_queue.qsize()

[andrewgodwin]

I'd just have one top-level function called communicator.receive_nothing that raises an (assertion?) error if it does receive something, that just wraps receive_from and catches the TimeoutError.

[dgilge]

I also thought about doing it that way. But as far as I understand the communicator is closed after this exception which is not what I want in some use cases...

[andrewgodwin]

Ah yes, the timeout will cancel it. I still think calling it receive_nothing makes sense though, and implement inside that as you see fit (using queue empty detection is fine)