9

It's always so funny when a person starts using multiprocessing in Python, because if there's "multi", obviously THIS is the thing that should free the person from a headache of having GUI frozen. You know, because it does "multiple" ehm... stuff..... at once....... yeah. And it's popular, it must work for me too! Oh how often I see this. :D

Stupidly enough that's not entirely a user's fault, but Python's as naming things with "multi" doesn't end up well basically with anything. I bet if there was such thing as multipointer in C half of the beginners would be totally fucked and the other one would just break their machines beyond repair with a joy.

Yet... reading the damn documentation should be a requirement before using threading or multiprocessing to prevent the confusion, because there's this funny difference between multiple threads and multiple processes which will haunt you unless you see what's what and use it correctly.

Comments
  • 2
    All I know is that if you're making a GUI application you finna need some threads. I haven't ever had a need to use multi processing
  • 0
    @harleywewax It's good for dumping a lot of values into multiple processes to speed up things. Of what I've seen, it's mostly used for a lot of computations, because well... GIL and Python itself don't like that by default.

    Other than that I still haven't found a proper use for that, hehe ^^
Add Comment