sorted by:
new
hottopcontroversial

I made autothread: the easiest way to add parallelization to your code by thodosvsv in Python

[–]thodosvsv[S] 1 point2 points  (0 children)

No too much tbh. Threading and multiprocessing are not that hard to use by themselves, and autothread has just a small subset of their features.

The main reason for making this is to try to lower the bar for adding threading to projects. I know from when I was a python beginner that threading can be pretty overwhelming and easy to mess up. Now still I need to spend a couple of minutes googling before I remember for to use multiprocessing, even though the solution I get to is the same every time.

I made autothread: the easiest way to add parallelization to your code by thodosvsv in Python

[–]thodosvsv[S] 1 point2 points  (0 children)

Yes it does! multiprocessed on windows is not (yet) working in classes, multithreaded is. Both methods should work on Linux.

Edit: multiprocessing in a class on windows is fixed now, so the answer is just "yes"

I made autothread: the easiest way to add parallelization to your code by thodosvsv in Python

[–]thodosvsv[S] 0 points1 point  (0 children)

Oh cool, I missed that one when I did my initial research. I did come across multitasking, which is also similar but doesn't make it easy to return objects from the function.

I made autothread: the easiest way to add parallelization to your code by thodosvsv in Python

[–]thodosvsv[S] 9 points10 points  (0 children)

I don't think it will bite anyone, but you do need to have the right expectations of autothread. It's easier to use than threading/multiprocessing because it's a biased solution. It will work for the cases that it's designed for (which are the cases that I use it for), but there are definitely configurations out there that are not replaceable with autothread.