μparallel - oversimplified helper for easy parallel functions execution
Yes, it's oversimplified:
```python
from uparallel import uparallel
import requests
@uparallel(3)
def wikipedia(word):
return requests.get(f"https://www.wikiwand.com/en/{word.capitalize()}")
results = [wikipedia(word) for word in 'fork spoon spork knife cup home'.split()]
for line in results:
print(line.url, line.status_code)
```
So, `unparallel(num)` is a wrapper for any function to execute `num` of them in parallel.
There's three limitations:
1. It will wait until last of calls finish their execution
2. It will break on any execption, so catch it inside the function
3. Returned result is a thin wrapper, not result of function itself.
Last one need more explanation. Instead of result of function you will got a special proxy object. It will behave more or less like your normal object (like in this example with `requests`). If it's not, call `result.wait()` or even just `result()` instead of just `result`.
```python
@uparallel(2)
def add2(x):
return x+2
results = [add2(x) for x in range(10)]
for y in results:
print(y()-2, y)
```
And don't afread to read the code, it's less than 100 lines long.
Metadata
Release files for uparallel 0.1.0
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 |
|---|---|---|---|---|
| uparallel-0.1.0.tar.gz | 2.1 kB | Without provenance | Details for uparallel-0.1.0.tar.gz |
Release files / uparallel-0.1.0.tar.gz
| Download URL | uparallel-0.1.0.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
58ded0854b87870a01d37e24b265de4416c3b6e44e01671f3a8251c912094ceb
|
|
BLAKE2b-256 checksum How to use checksums |
a3b99ab751547fedfb849da32d30292f95633b4797c932d214ee34f7a8e8a8f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for uparallel 0.1.0
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.