Details
Description
Hey here,
I have been following up the development of QtAsyncio. The work that have been ongoing is very nice but quite some things are missing. It is not too many, but that requires some more work to finish and polish QtAsyncio.
I have spent +100h on trying to figure out what to fix and fix it. Unfortunately, my knowledge of Qt objects and networking are slowing me down a lot. I would really like to push forward the development of this library.
Right now, a quite considerable asset is missing: support of aiohttp. In other words, the part of QtAsyncio that needs to be now implemented is "Working with socket objects directly".
I attach a script that can let you further investigate the issue; you can switch between asyncio.run() and QtAsyncio.run() to compare the results. Just comment and uncomment what you need to test it out in the `if _name_ == "_main_"`.
Changes to QtAsyncio from Adrian Herrmann which are not yet released did not bring the missing part I mentioned, but he implemented many things required by an event loop according to asyncio's definition.
Is there any taskforce to move forward on QtAsyncio? I am willing to help of course.
Best regards
Loan Guilbaud