On Fri, 9 Sep 2016 07:28 pm, Chris Angelico wrote: > We don't > have a problem with threading and multiprocessing having very similar > APIs, do we? Yet they exist to solve distinctly different problems.
Surely not? I would think that threading and multiprocessing are two distinct implementations of the same problem: how to run two or more chunks of code at the same time. In CPython we usually say "use threads for I/O bound tasks, processes for CPU bound tasks" but that's only because of the GIL. One doesn't need such a distinction in Jython or IronPython. -- Steve “Cheer up,” they said, “things could be worse.” So I cheered up, and sure enough, things got worse. -- https://mail.python.org/mailman/listinfo/python-list
