Matthias Urlichs
Matthias Urlichs
Of course I meant "Reading the **response**." I fixed the commit's comment and re-uploaded.
Any progress? this change is necessary on py3.5.
this is required to fix https://github.com/Polyconseil/aioamqp/issues/50
> You are probably right that in hindsight individual tasks could also work. But since this is existing code that I'm trying to interface with, that choice for threads has...
Well, it's a good example for a guide anyway. The anyio-ish solution is async def close_when_done(main): try: await main() finally: await Tortoise.close_connections() anyio.run(close_when_done, your_main_code) asyncio's standard calling convention would look...
https://github.com/M-o-a-T/anyio_serial.git does that. Granted that delegating absolutely everything to a worker thread is not an optimal solution by a long shot, but at least it gets the job done.
Thanks, that file did need some attention. :-/
Just use an event.
Short answer: no. Long answer: asyncio libraries ten to be an unstructured hodgepodge of callbacks (just like asyncio itself … SCNR). We don't want to replicate that. IME it's easier...
Well, I do agree that we should have a "basic asyncio patterns > equivalent anyio patterns" guide. And yes some libraries are trivially ported. However, as soon as things become...