Python Environment Provider (Preview)

This node provides a Python environment specification to downstream Python-aware nodes such as Python Script nodes. The environment is defined using pixi, a fast package manager built on top of conda-forge and PyPI that ensures reproducible Python environments across different platforms (Windows, Linux, macOS).

The node offers three ways to specify the Python environment:

• Packages: Define packages directly in a simple table format. Specify package names, sources (Conda or PyPI), and optional version constraints. This is the easiest method for simple environments.
• TOML editor: Manually write or edit a complete pixi.toml manifest file. This provides full control over all pixi features including channels, platforms, and complex dependency specifications. The TOML format follows the pixi project specification.
  Example TOML:

  [workspace]
  channels = ["knime", "conda-forge"]
  platforms = ["win-64", "linux-64", "osx-64", "osx-arm64"]
  
  [dependencies]
  python = "3.13.*"
  knime-python-base = "*"

• YAML editor: Import an existing conda environment.yaml file. The node automatically converts this to pixi format and configures it for all major platforms (Windows, Linux, macOS Intel/ARM).

Environment resolution: After specifying the environment using any of the above methods, click the "Resolve Dependencies" button. This runs pixi to resolve all package dependencies and verify that the environment can be created on all configured platforms. The resolved environment is stored in a lock file, ensuring that the exact same package versions are used regardless of when or where the workflow is executed.

Using the environment: The output port of this node provides a Python Environment specification that can be connected to Python Script nodes and other Python-aware KNIME nodes. These downstream nodes will automatically use the specified environment when executing Python code.

Note: The actual Python environment is not created by this node. Instead, downstream Python nodes will automatically create and cache the environment on first use based on the lock file specification.