Asynchronous transcription via asyncio

[serozhenka]

Using asyncio will be greatly beneficial in the use case of transcription as most of the time the client waits for a response on a socket when your servers are doing all the great work.

concurrent.futures implementation still works but is not as good for two main reasons:

• The hardware capabilities limit the number of executor workers (or just threads), unlike asyncio's lightweight coroutines
• concurrent.futures module issues blocking operations which can block the event loop in a fully asynchronous environment

Hope for positive feedback on that!

[ploeber]

Hey @serozhenka , great feedback!
It's actually on my TODO list for v 1.0.0 to introduce an asyncio client.

I plan to introduce it before v.1.0 so there's a transition period where both asyncio and the threading solution with the _async() functions can be used.

[serozhenka]

Sounds great!
Do you have an approximate ETA of when can I expect it to be ready?

[ploeber]

aiming for Q4 2024

[victorct-tradeengage]

+1, although I would suggest to use AnyIO so people using Trio can also use the library.

[amirreza8002]

hi
i think it should be mentioned in docs that concurrent.futures.Future is not awaitable

[barapa]

Any update on this?

[scottyeung]

Any update on this?

Same here!

[aigrinder]

aiming for Q4 2024

Hey @ploeber, will this still be ready by end of the year?

[david-oliveira-br]

@ploeber Any updates? Looking forward to this!

[yovelcohen]

I would like to pile on the pressure for this one :) the current implementation has us bending upwards and backward to fit into our flows.

[serozhenka]

It's funny how adding asynchrony support takes nearly half a year while already ~8 people ask for this :)
@ploeber @marcusolsson do you need any help with that?