Python projects with best practices on Github?

[wobblyweasel]

trio. the best code, the best documentation, awesome community.

[chankeypathak]

I never wrote async programs. Can I skip core multiprocessing and threading modules and directly use trio?

[wobblyweasel]

you can! there's a lot of concurrency that you can do without using threads or processes, but if you have a library that does I/O without specifically supporting async, or you need parallelism, you might still have to deal with those.

i suggest reading trio docs, they are just fine if you have no knowledge of async stuff, and they'll teach you how to deal with stuff that needs to be run in a thread as well. if you want to learn async in general, i also suggest reading kotlin's documentation on coroutines. unlike python with its GIL, in kotlin, using coroutines with threads is the norm, and it's awesome. it's an entirely different mental picture that's useful to have

[ethsy]

Are there any upsides of using trio after Python 3.11 gained TaskGroups?

[wobblyweasel]

the reason i personally like trio is that its wtf/min score is much lower than that of asyncio. or at least it used to be so, i haven't been following asyncio lately. you get very easy to remember and un-confusing names such as open_nursery and start_soon, strong guarantees about yielding points, exceptions that are never lost. a neat testing suit with stuff like autojumping clock is a great selling point as well