play_sounds VS AIOHTTP

play_sounds is a library that provides a simple API over the cross-platform idiosyncrasies that Python's sound playing ecosystem presents. It lets you play sounds in Python scripts easily. I recently added an async/await compatible API to it.

I added an async API to play_sounds and better support for making sure that spawned player processes are killed when the parent process doesn't shut down cleanly. play_sounds provides a simple API over the cross-platform idiosyncrasies that Python's sound playing ecosystem presents.

> AIOHTTP: The Python int constructor is used to parse Content-Lengths and chunk-sizes, so _, +, and - are misinterpreted.

Fun. I believe the fix is incomplete here[1]. Python's int() constructor accepts integers comprised of any unicode numeral, for example, int("٦٦٦") == 666, and "٦٦٦".isdecimal() == True.

[1] https://github.com/aio-libs/aiohttp/pull/7663/files#diff-197...

aiohttp

If you want speed, I would try to rewrite everything using an asynchronous library like aiohttp.

requests does not support async out-of-the-box, so we will use aiohttp to avoid complications. requests can do the job, and there is no substantial performance difference. But the code is more readable using aiohttp.

I'm using aiohttp to build an API server that sends TCP requests off to a seperate server. The module that sends the TCP requests is synchronous and a black box for my purposes. So my problem is that these requests are blocking the entire API. I need a way to wrap the module requests in an asynchronous coroutine that won't block the rest of the API.

aiohttp - Everything that I need and nothing that I don't.

Use aiohttp to download the content of each page of lists. As of this Code Review post, this is the only step we execute.

Reminds me of this post from 5 months ago, but it was for a Python library. I made a discussion thread on the aiohttp repo and someone ended up contacting the reddit admins about it. The problem seems to be resolved now.