Python Script

The node allows executing a Python script in a local Python 3 environment. The environment has to be configured under File → Preferences → KNIME → Python or via flow variable, as described in the KNIME Python Integration Guide . Multiple input and output ports of various types can dynamically be added to the node and used in the script. See sections Ports and Editor below for a description of all available inputs and outputs, and how they can be accessed in the Python script. Furthermore, the node allows to import Jupyter notebooks as Python modules via the knime.scripting.jupyter module that can be imported in the script. See the API Documentation for a detailed description of the full API.

The node brings significant performance improvements over the nodes of the legacy KNIME Python Integration and enables working with larger-than-memory data. More details on how to transition to the node's new scripting API can be found here . There are also example workflows that further illustrate its use here as well as example templates on the Templates tab of the node.

Please consider the following prerequisites before using this node:

• The packages py4j and pyarrow , are required to be installed in your Python 3 environment in specific versions. We recommend to create a new Conda environment that contains these packages via File → Preferences → KNIME → Python.
• Columnar Backend should be enabled for best performance.

Input ports

1. Type: Table
   Table
   No description available

Output ports

1. Type: Table
   Table
   No description available

Input object (pickled) (Dynamic Inport)

An input object. Input objects are automatically unpickled for you. You can access them via knio.input_objects . For example, the first input object can be accessed like this: knio.input_objects[0] .

1. Type: Python

Input table (Dynamic Inport)

An input table. You can access input tables via knio.input_tables . For example, the first input table can be accessed like this: knio.input_tables[0] . Each table is an instance of type knio.Table . Before being able to work with the table, you have to convert it into, for example, a pandas.DataFrame or a pyarrow.Table . Please refer to the KNIME Python Integration Guide to learn how to do this, or take a look at one of the templates on the Templates tab of the node.

1. Type: Table

Output table (Dynamic Outport)

An output table. The table has to be populated via knio.output_tables in your script. For example, to populate the first output table, assign it a value like this: knio.ouput_tables[0] = . The assigned value must be an instance of type knio.Table which can be created from, for example, a pandas.DataFrame or a pyarrow.Table . Please refer to the KNIME Python Integration Guide to learn how to do this, or take a look at one of the templates on the Templates tab of the node.

1. Type: Table

Output image (Dynamic Outport)

An output image. The image has to be populated via knio.output_images in your script. For example, to populate the first output image, assign it a value like this knio.output_images[0] = . The assigned value must be a bytes-like object encoding a PNG or SVG image.

1. Type: Image

Output object (pickled) (Dynamic Outport)

An output object. The object has to be populated via knio.output_objects . For example, to populate the first output object, assign it a value like this: knio.output_objects[0] = . The assigned value can be of any type that can be pickled. It will automatically be pickled for you.

1. Type: Python

External resources

• API Documentation
• Examples in the "Python Script Space" on the KNIME Hub