This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Claudiu.Popa
Recipients Claudiu.Popa, Jim.Jewett, brett.cannon, dholth, eric.araujo, pitrou, steven.daprano
Date 2014-04-27.13:00:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Added a new patch with improvements suggested by Jim. Thanks!

I removed the handling of processes=1, because it can still be useful: having a background worker which processes the files received from _walk_dir. Also, it checks that compile_dir receives a positive *processes* value, otherwise it raises a ValueError. As a side note, I just found that ProcessPoolExecutor / ThreadPoolExecutor don't verify the value of processes, leading to certain types of errors (see issue21362 for more details).
Jim, the default for processes is still None, meaning "do not use multiple process", because the purpose of ProcessPoolExecutor makes it easy for it to use processes=None=os.cpu_count(). Here we want the user to be explicit about wanting multiple processes or not.
Date User Action Args
2014-04-27 13:00:20Claudiu.Popasetrecipients: + Claudiu.Popa, brett.cannon, pitrou, eric.araujo, steven.daprano, dholth, Jim.Jewett
2014-04-27 13:00:19Claudiu.Popasetmessageid: <>
2014-04-27 13:00:19Claudiu.Popalinkissue16104 messages
2014-04-27 13:00:19Claudiu.Popacreate