Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • "So when threading is used, there is only a single operating system level thread while python creates pseudo-threads which are completely managed by threading itself but are essentially running as a single process. " That is not true. Python threads are real OS-threads. What you are describing are green threads, Python does not use that. It's just that a thread needs to hold the GIL to execute Python-bytecode which makes thread-execution sequential. Commented Feb 13, 2019 at 16:09
  • Now in case of self-contained instances of execution, you can instead opt for pool. But in case of overlapping data, where you may want processes communicating you should use multiprocessing.Process. What pool? The multiprocessing library has a Pool, so this doesn't make much sense. Commented Feb 9, 2020 at 16:22