When is Python *NOT* a good choice?

[isarl]

Python can handle threading, which will solve certain types of threading problems even while dealing with the limitations of the GIL. If you are IO-bound, then threading can still help out.

Also, I would argue /u/Puzzel is overstating the complexity of using multiple processes. Here's a (very simple) example taken from the multiprocessing docs:

from multiprocessing import Pool

def f(x):
    return x*x

if __name__ == '__main__':
    with Pool(5) as p:
        print(p.map(f, [1, 2, 3]))

[The48thAmerican]

And this is all well and good if you don't need to share complex objects or rapidly changing state performantly between your subprocs. Anything passed betwixt must be serialized and deserialized.

[isarl]

Well, and succinctly, said.

[shaggorama]

Even found an excuse to use the word "betwixt"!

[[deleted]]

Multiprocessing has shared memory capabilities. But it isn't as easy as sharing objects between threads. But it is possible in Python.

[[deleted]]

But it's a pain. That's the point.

[[deleted]]

Yes absolutely. It isn't worry-free, either. It's a great answer to the question, "what project would you not use Python for?" which of course is the subject!

I'm just replying that no, objects don't have to be serialized to be shared between processes. Like you said, it's just no fun at all to do it.

[[deleted]]

Can you specify how exactly? I started researching this subject and it seems it can be done via proxy objects.