Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

77%
+5 −0
Q&A Readable syntax for executing many callables with useful side effects

The map operation is a typical concept from the functional programming paradigm. However, side-effects are a typical example of something that does not fit functional programming well. As a resul...

posted 9mo ago by mr Tsjolder‭

Answer
#1: Initial revision by user avatar mr Tsjolder‭ · 2023-08-11T21:59:46Z (9 months ago)
The `map` operation is a typical concept from the functional programming paradigm.
However, side-effects are a typical example of something that does not fit functional programming well.
As a result, `map` is probably not what you want to use.

As an alternative, you can just use the [`apply`](https://docs.python.org/3/library/multiprocessing.html#multiprocessing.pool.Pool.apply) method of the `Pool` class as follows:
```python
import multiprocessing

pool = multiprocessing.Pool
for f_i in f:
    pool.apply(f_i)
```

Given that your context seems to be IO-bound, it might also be useful to consider thread pools instead of process pools.
Threads are a bit more lightweight, but due to the [GIL](https://wiki.python.org/moin/GlobalInterpreterLock) they are only useful for tasks where the CPU has to wait for IO anyway.
```python
from concurrent.futures import ThreadPoolExecutor

with ProcessPoolExecutor() as pool:
    for f_i in f:
        pool.submit(f_i)
```
FYI: the `concurrent.futures` package also has a ProcessPoolExecutor with the same interface.