Vincent Michel

@Jc2k > I think for aiostreams auto-generating a chaining interface would require some fairly awful looking dynamic code that might not gel well with typing and probably isn't worth it?...

Interesting... So it cannot be a loop, it probably shouldn't be a policy either, and a coroutine is not enough cause we need proper cleanup on shutdown. Maybe it should...

Hi @plammens and thanks for your report! We already had a similar discussion here: https://github.com/vxgmichel/aioconsole/issues/90#issuecomment-997997618 Still, your suggestion about setting the non-blocking mode only when necessary is interesting, I'll think...

> Would that mess up the second one, which is still waiting? Yes it would, so the implementation would have to take care of that. Another solution would be to...

### Extra note: It is not trivial to manage those accesses to the local database while maintaining a cache in a consistent way, like we do for the manifests. Luckily,...

> (required by PyQt signals) I'm not sure pickle support is required for PyQt signals. I ran a quick test on master and it seems there's not problem with providing...

Hi @danielloader, sorry for the delay > Found this library and want to say thanks, it's absolutely brilliant for my usecase of merging multiple AWS Kinesis streams into a single...

Hi @AIGeneratedUsername and thanks for the report, > What is the reason of the current implementation? Good catch. The stream operators provided by `aiostream` have quite an overhead although I...

> This functionality has been implemented That's great! Is the reboot still required after the update?

There is a bit of explanation in [BaseEventLoop.run_until_complete](https://github.com/python/asyncio/blob/master/asyncio/base_events.py#L374-L382): ``` python try: self.run_forever() except: if new_task and future.done() and not future.cancelled(): # The coroutine raised a BaseException. Consume the exception #...