Why does a result() from concurrent.futures.as_completed() occasionally return None?
Why does a result() from concurrent.futures.as_completed() occasionally return None? Question: I’ve been writing a fairly complex series of modules to help test our poorly documented networking gear, this one focused on trying the various passwords used across the company. I’ve been using the concurrent.futures module to speed things along by testing many devices in parallel …