Pyrseus’ Executor Classes¶

The following is a comprehensive list of all of the concurrent.futures.Executor subclasses provided by Pyrseus.

Serial-only Executors¶

These serial-only executors non-concurrent ones that are suitable for light workloads and troubleshooting. They allow users to retain their executor-based control flow instead of requiring users to have separate serial and parallel driver functions. See the notebooks linked on the left for usage examples.

Executor	Pickler	Errors at	Notes
`InlineExecutor`	n/a	`fut.result()`	serial mode, useful for light workloads and debugging
`PInlineExecutor`	`pickle`	`fut.result()`	like `"inline"`, but simulates the pickling done by concurrent executors that use `pickle`; for troubleshooting pickling problems
`CpInlineExecutor`	cloudpickle	`fut.result()`	like `"pinline"`, but uses cloudpickle
`NoCatchExecutor`	n/a	`exe.submit(...)`	like `"inline"`, but has intentional non-standard exception handling
`PNoCatchExecutor`	`pickle`	`exe.submit(...)`	`"nocatch"`-style exception handling with `"pinline"`-style pickle testing
`CpNoCatchExecutor`	cloudpickle	`exe.submit(...)`	`"nocatch"`-style exception handling with `"cpinline"`-style pickle testing

Single-host Concurrent Executors¶

When only single-host parallelism is needed, the following executor provides some benefits over the built-in ProcessPoolExecutor.

Executor	Pickler	Errors at	Notes
`CpProcessPoolExecutor`	cloudpickle	`fut.result()`	`"process"`, but uses cloudpickle for serialization