This release is a pre-release and may not be stable for production use.
which simply defers the calculation of any function
or method off process.
The decorated function returns a lazy object,
which will just attempt to retrieve the actual
return value of the function when it is about to
be used in any Python expression.
Currently, the only public member in the
project is the "parallel" decorator, which is used just as:
@parallel
def retr_url(url):
return urllib.urlopen(url).read()
-And voilá - upon calling the above "retr_url",
execution simply proceeds, while Python multiprocessing
creates another process to actually download the url
contents.
Unlike Python's 3.2 concurrent.futures, there is no
setup needed - just decorate your function
and you are all set-up to go.
1 maintainer
Metadata
1 maintainer
Release files for lelo 1.0rc1dev
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 | |
|---|---|---|---|---|
| lelo-1.0rc1dev.tar.gz | 2.9 kB | Without provenance | Details |
Release files / lelo-1.0rc1dev.tar.gz
| Download URL | lelo-1.0rc1dev.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bddaf4e73969b5730289b881f1a725734604d1482e65bcfbf20eeaa6878f370d
|
|
BLAKE2b-256 checksum How to use checksums |
93496f5875e5e1ffd05bb0f9a9b90d0c39fe853c98b41337d85868a86b231e19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for lelo 1.0rc1dev
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.
