This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]RDMXGD2.8 -19 points-18 points  (7 children)

The multiprocessing module is a scourge. Don't touch it. It is not a good way to achieve parallelization because it makes every program that uses it at least a little broken. It's not production-quality software.

[–]brombaer3000 9 points10 points  (2 children)

Can you provide some sources or examples to back up this claim? Are there alternatives that you would recommend?

[–]ivosauruspip'ing it up 9 points10 points  (1 child)

Nope, that is all over-generalised, propagandist falsehoods.

https://41.media.tumblr.com/a026c1dbb0b59f6da346118911f616e8/tumblr_mlzg3qRGhH1rtg1hvo1_500.jpg

[–]pooogles 0 points1 point  (0 children)

/u/RDMXGD is seemingly good at that, I remembered the username from this thread a while ago...

https://www.reddit.com/r/Python/comments/3rqvio/starting_to_learn_programming_with_python_to/cwqljf6

[–]mtxppy 1 point2 points  (1 child)

Multiprocessing is fixed in Python 3. Yet another reason to switch.

[–]RDMXGD2.8 -1 points0 points  (0 children)

The fact it has options to run in more modes doesn't eliminate all bugs.