This is an attempt to address the discussion in #250.
The change is to propose using multiprocessing.dummy (which is a threading wrapper) on Windows to avoid the restriction Safe importing of main module (which requires the downstream tools to be updated to work). This way can keep parallelism but not requires the downstream tools to be modified.
Plus, this change adds an Azure pipeline yaml to exercise the test suite on Windows machines.
This is an attempt to address the discussion in #250.
The change is to propose using multiprocessing.dummy (which is a threading wrapper) on Windows to avoid the restriction
Safe importing of main module
(which requires the downstream tools to be updated to work). This way can keep parallelism but not requires the downstream tools to be modified.Plus, this change adds an Azure pipeline yaml to exercise the test suite on Windows machines.