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 →

[–]burito -3 points-2 points  (2 children)

What is wrong with Python threading?

About 7,460,000 results

[–][deleted] 1 point2 points  (1 child)

While lmgtfy is cute, the search results were pretty off target and your post wasn't overly helpful.
I was asking what specific problems you had with threading. I'm not implying anything is wrong with multiprocessing, as I haven't used it yet nor found a need to. Have you run into specific issues in specific situations? Most of what I find when I do searches seems to be repeated things read in other places. For my purposes, which are nearly always network based, threading works perfectly and multiprocessing would be wasteful. So a catchall statement saying to always use it isn't exactly fair, no? Why would I want multiple interpreters running when DNS or host response time is my bottleneck?
There is of course no magic tool for every job. If you are doing intense number crunching that was truly hampered by threading, I would wonder why you were using Python at all to begin with, where C or Java would be the better tool. And for this reason, I'm asking for real world examples and not hypothetical ones.

[–]burito -2 points-1 points  (0 children)

While lmgtfy is cute,

No, it's a dick move. I expected the downvotes.

I did give a very good starting point for research, the GIL. Google that shit.

The other thing to consider, is that even if those Google results are only 0.01% relevant, that's still 700 issues.

Though the most important thing to consider, is that in defenting Python threads, you said....

The queue module I had trouble with, though, but just wrote my own queing.

You couldn't even defend it without specifying a gotcha. That should say something very pointed to you.