Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32.1k
Closed
Description
Documentation
Attending a tutorial on distributed computation at KiwiPyCon, it struck me that the concurrent.futures module wasn't even mentioned, even though it is a better option than using the threading or multiprocessing modules directly for local IO bound or CPU bound operations (seehttps://peps.python.org/pep-3148/ for background).
Reviewing the docs, one notable omission is that neither of the lower level modules provides an explicit pointer to the higher level interface. The only cross-references are:
- the threading docs recommend ProcessPoolExecutor as a way to work around the CPython GIL (they don't reference ThreadPoolExecutor)
- the multiprocessing docs recommend ThreadPoolExecutor over multiprocessing.dummy.Pool (they don't reference ProcessPoolExecutor)
It would make sense to provide pointers early in the low level docs for cases where the high level API is more appropriate