This release is a pre-release and may not be stable for production use.
ezFutures
ezFutures is a Python parallel computation tool that provides the user API similar to that of concurrent futures, with various parallelism backends.
Install
pip install ezFutures
Getting started
First, we need to import the class:
from ezFutures import ezFutures
In order to start working with ezFutures, you must instantiate the class object. The most important parameter to set is the n_procs parameter which defines the number of processes to run in parallel.
ez = ezFutures(n_procs=19)
From there, you can submit jobs in a sequential manner, just as you do with concurrent futures. However, because ezFutures default parallelism backend is not concurrent futures, merely submitting a task will not start the job. You have the option of using concurrent futures process pool as the parallelism backend (we will update documentation in the future to describe this)
def some_task(elem):
return(elem)
for i in range(10):
ez.submit(some_task, i)
You can start the jobs by invoking results method, just as you would with the concurrent futures API.
ez.results()
# Progress: |██████████████████████████████████████████████████| 100.0%
# [1, 2, 7, 0, 8, 3, 5, 4, 9, 6]
The 10 tasks submitted are done in parallel asynchronously, which is why the returned results order is jumbled.
In case there are errors, you can retrieve the stacktrace by invoking errors method.
ez.errors()
The default parallelism backend will try the tasks 3 times (configurable using n_retries parameter when initializing ezFutures) before marking the task as a “failed” task.
Metadata
Release files for ezFutures 0.0b21
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ezFutures-0.0b21.tar.gz | 6.7 kB | Without provenance | Details for ezFutures-0.0b21.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ezFutures-0.0b21-py3-none-any.whl | Python 3 | none | any | Details for ezFutures-0.0b21-py3-none-any.whl |
Total release size: 15.0 kB
Release files / ezFutures-0.0b21.tar.gz
| Download URL | ezFutures-0.0b21.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b2af00c507264ff356516edde727798e7457bd60c224b667ef78ed7b997147f
|
|
BLAKE2b-256 checksum How to use checksums |
ae74f383439d35b5aa1995593d363ff5a6a4327f8a39746a644f29849788674c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.6.7
|
Release files / ezFutures-0.0b21-py3-none-any.whl
| Download URL | ezFutures-0.0b21-py3-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4eb7b817b2150167a6d83fed9e65a752604bec72142b97540819dcac972cdf3d
|
|
BLAKE2b-256 checksum How to use checksums |
666012481fdd8a3388873bc91f6e63bafb8cba08cf6c073eda1e56b9a79f93a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.7.1
|
Security for ezFutures 0.0b21
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.