Utilities for working with KNIME workflows and data.
Via the Workflow class, a KNIME Workflow can be run via KNIME’s batch executor (requires KNIME be installed on the local system). Inputs to the “Container Input (Table)” nodes in a KNIME Workflow can be supplied as either Python dicts or pandas DataFrames. Likewise, outputs captured from “Container Output (Table)” nodes are provided back as either Python dicts or pandas DataFrames.
- TODOs:
add handling for setting of workflow variables - only via Container Input (Variable) nodes? - also via batch executor variable settings?
add handling for Container Input/Output (JSON) nodes
support remote workflows
1 maintainer
Metadata
1 maintainer
Release files for knime 0.11.6
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 |
|---|---|---|---|---|
| knime-0.11.6.tar.gz | 9.2 kB | Without provenance | Details for knime-0.11.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| knime-0.11.6-py3-none-any.whl | Python 3 | none | any | Details for knime-0.11.6-py3-none-any.whl |
Total release size: 30.3 kB
Release files / knime-0.11.6.tar.gz
| Download URL | knime-0.11.6.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e122813b262ee85e54037b30f4e6618e8b070c6045d0ee295bb77eac60c633c9
|
|
BLAKE2b-256 checksum How to use checksums |
60eceaf90d8919594d2b95045c97c049850210d7d4acd47a83e429f342477407
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.24.0 setuptools/46.1.3.post20200330 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.7.7
|
Release files / knime-0.11.6-py3-none-any.whl
| Download URL | knime-0.11.6-py3-none-any.whl |
|---|---|
| Size | 21.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5c334767e58fcc033bfad6bc8ee765796814b895b082cbc536d5c92a6c0b1c72
|
|
BLAKE2b-256 checksum How to use checksums |
40881af7a68e8485ffb4d89307639cf672d51488b914e4ce4194a91f8cf7026d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.24.0 setuptools/46.1.3.post20200330 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.7.7
|
Security for knime 0.11.6
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.
