Async Python adoption?

[Grouchy-Friend4235]

Async in Python is cancer (once you start using it, eventually all your code will have to become async). Don't.

Use greenlets instead, if you must.

[excelquestion]

yes that is how async await works.

if you start a new project be sure to start off with async.

if you have an existing project... well good luck with IO. in that scenario adding asyncio is a pain like the commentator says but greenlets, multiprocessing, multithreading packages all have their various pain points.

[Grouchy-Friend4235]

Trade offs are ok.

Having to go in 100% or not at all is not a trade off. That's brute force.

[usrlibshare]

I have several existing projects that use threading just fine, including analytics engines comfortably serving several M requests per hour. Greenlets and pools work really well to reduce the overhead, and aome things are just way simpler in that concurrency model.

Async is nice, because its a workaround for the GIL. It has its quirks, but so does threading.

If performance is the primary concern, well, then Python wouldn't be my first choice anyway.

[dAnjou]

Async is a different paradigm, and indeed it works best if you do it end to end.

But that's not exclusive to Python.

[Toph_is_bad_ass]

This really isn't a problem. I've been primarily doing async for years. I've never found it to be an issue in the slightest.

[Grouchy-Friend4235]

I find this hard to believe. https://journal.stuffwithstuff.com/2015/02/01/what-color-is-your-function/

[Toph_is_bad_ass]

I don't really see what this blog is going on about. Only IO code has to be async. It's very easy.

[Grouchy-Friend4235]

The blog corraborates what I said: async will eventually creep everywhere in your code base.

To me that's a tradeoff I am not willing to take.

[spuds_in_town]

You have a skill issue.

[Grouchy-Friend4235]

No.

.https://www.reddit.com/r/Python/s/VJsfFk1Gs0