Traverse invoke
A nested method [computation model] for nested data
This shit is a blessing. I don’t know anything like this except maybe lambda. I’ll think about Turing-completeness and meta complexity of this.
Please do yourself a favor and read the source.
Docs not yet available, since the whole computation model needs to be formed, which requires some experience of using current version.
Documentation: https://traverse-invoke.readthedocs.io (uder development. maybe).
Features
Invoke methods by their path in module tree.
Pass arguments as nested closures for methods.
Modify invocation path in runtime (the most exiting thing).
Basic Usage
Invoke method
import sys, traverse_invoke
method = 'sys.version'
names = {
'sys':{'version':sys.version}}
}
args = { 'version':'foobar'}
traverse_invoke.entry_traverse(args, method, names)This will invoke sys.version(**{version:foobar})
Traverse
see test
History
0.1.0 (2020-01-14)
First release on PyPI.
1 maintainer
Metadata
1 maintainer
Release files for traverse-invoke 0.1.1
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 |
|---|---|---|---|---|
| traverse_invoke-0.1.1.tar.gz | 12.1 kB | Without provenance | Details for traverse_invoke-0.1.1.tar.gz |
Release files / traverse_invoke-0.1.1.tar.gz
| Download URL | traverse_invoke-0.1.1.tar.gz |
|---|---|
| Size | 12.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4aafda60b1aabdec47b0313f271bc8713ca16ca2ddeec9c85dcdc0a1626773ae
|
|
BLAKE2b-256 checksum How to use checksums |
ae96471f89cf4fab9fc18ee10a0e045e020aadb788277f7f7faec405cb331d92
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.14.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/42.0.2 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.7.3
|
Security for traverse-invoke 0.1.1
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.
