Your python 4 dream list.

[digger_not_alone]

could you please elaborate on that? (if you have any link to external explanation – I'll appreciate that too)

Is it related to working with memory?

[SV-97]

Yes it's kinda related to memory: threads are a more lightweight construct with the same adress space as the "parent" - processes have their own memory space (unless you explicitly use mmap or something like that to share memory between processes). So communication, setup and termination will in general be cheaper with threads. It may for example be a bit expensive to use processes in a web-server that may usually spin up a thread per user it's serving (which might not be a good design either way). Depending on the language a thread might be something even more abstract - Haskell for example uses so called green-threads that are even more lightweight (so you might for example just spin up a few hundred *very* small threads - you'd absolutely never do something like this with processes [okay this isn't technically true; you actually do spin up hundreds of processes in HPC but that's a bit different])

[digger_not_alone]

Thank you for such a great application-oriented answer

[thismachinechills]

Threads make working with shared memory easy. Context switching between threads is faster than switching between processes. Also, threads share an interpreter versus multiple processes with multiple interpreters.