Closed leplatrem closed 7 years ago
The backport is a backport of Python 3.2's ThreadPoolExecutor. That said, I guess this is trivial enough to incorporate in the backport.
You're right, there is no error in python 3.2.
I just wanted to let you know because I came into it, but I don't think it is crucial ;)
well, why does this backport keep API of py32 which is too old for production use.
Both max_workers
is 0 and None ( #54 ) will silently lead to an executor with no worker, that is really too bad
The changes made in the newer versions of concurrent.futures require Python core changes to work. That's why I haven't backported any newer versions. For reliable process pools, you must upgrade to Python 3.x. As for this particular change, I'll make it happen this week when I have the time.
Fixed in 09138538e446dbe7664bfab5b29fd2d51e625d4d.
Aha, thanks very much for such a quick response, and sorry for the late regards.
I noticed a difference when instantiated the executor with
ThreadPoolExecutor(max_workers=0)
. The backport does not raise, whereas the 3.5 raises a ValueError: