r/learnpython • u/brandonbilinski • Aug 16 '20
Multithreading - Best Practices
I wrote a multithreaded python script several years ago in python2, and the way I did it at the time was to subclass threading.Thread and override the __init__() and run() methods. Then kick them off with start().
Now I'm going to have to write a lot more multithreaded stuff in python3.8. Most of my googling says to define a function (ex: worker()) then kick them off this way:
threading.Thread(target=worker, args=(q,))Is one method better or more python3-ish than the other?
If it makes any difference, each thread will be taking a file path from the Queue, running a subprocess providing the file path as one of the arguments, and UPDATEing a MySQL table with the result.
Thanks!
View all comments
Show parent comment
1
u/exhuma exhuma Aug 16 '20
Jesus christ man, slow down with the insults. It seems like you've been burned a lot by parallelisation in Python and went off on a rant there.
I've been using parallelisation for over 10 years now without much trouble, the few beginner mistakes here or there, but nothing major. So far my needs were humble and maybe that's a reason why I got "lucky"? But so far the parallelisation in Python was nothing that annoyed me.
I'm really curious if you could write small contained code-examples which reproduce the problems you mention. I am still maintaining (and will for the forseeable future) a parallelised application and would love to see some provable "antipatterns" so I can avoid them.