aiohttp-aiofiles-tutorial VS aiofiles

We're going to structure this script like any other Python script. Our main module, aiohttp_aiofiles_tutorial will handle all of our logic. config.py and main.py both live outside the main module, and offer our script some basic configuration and an entry point respectively:

I'm unaware of a library that facilitates any of this, so unless I find one or more suitable libraries with this matter, then I'm looking at using Numba and either aiofiles or aiofile—I'm not yet sure what the difference between the two is—and writing my own encoder(s).

Aiofiles: Makes writing to disk (such as creating and writing bytes to files) a non-blocking task, such that multiple writes can happen on the same thread without blocking one another - even when multiple tasks are bound to the same file.

To solve this, you need an async version of function/library. hopefully, requests has a good async alternative- aiohttp. API structure is nearly identical to requests, so It won't be a big pain to migrate. for doing file I/O, there's aiofiles.