René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Why using synchronous get in flags_asyncio.py","articleBody":"When downloading the flags in \r\n```\r\nasync def get_flag(client: AsyncClient, cc: str) -\u003e bytes:  4\r\n    url = f'{BASE_URL}/{cc}/{cc}.gif'.lower()\r\n    resp = await client.get(url, timeout=6.1,\r\n                                  follow_redirects=True)  5\r\n    return resp.read()  6\r\n```\r\nit seems that we read the response using .read() which is synchronous, why don't we \r\n```\r\nreturn await resp.aread()\r\n```\r\ninstead? \r\n\r\nThe explanation seems to be for client.get() where it is doing network IO asynchrnously provided by httpx. But not for read()\r\n```\r\n6\r\n\r\n    Network I/O operations are implemented as coroutine methods, so they are driven asynchronously by the asyncio event loop.\r\n```","author":{"url":"https://github.com/ngokchaoho","@type":"Person","name":"ngokchaoho"},"datePublished":"2023-12-13T06:54:05.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/40/example-code-2e/issues/40"}