Skip to content
KNIME Documentation
Main Navigation Get startedBuildWork with KnimeAccount and adminRelease notesDeveloper tools
Community Hub
DevelopersKnime
Sidebar Navigation

Getting Started

Installation

User Guide

Release Notes

Install Extensions

Building Workflows

Components

Flow Control

Expressions

File Handling

Deployment

Integrated Deployment

Workflow Invocation

Best Practices

Advanced Features

AI Extension

Get Started

Build an Agent

Inject context with RAG

LLM Providers

Tutorials

Summarize product reviews

Product FAQ assistant

Restaurant agent

Your first local agent

Task extractor

Reporting

Kerberos

Extensions

Database

Overview

Tutorials

Read and filter data from a database

Write a transformed dataset to a database

Concepts

Ports and Sessions

Query Generation

Type Mapping

Deprecated Framework

Connecting

Connect: Dedicated Node

Connect: File-Based Database

Connect: Generic DB Connector

Register a JDBC Driver

Install Third-Party Driver Plug-in

Drivers on Hub and Server

Kerberos Constrained Delegation

Reading and Transforming

Read Data

Transform Data Visually

Run a Custom SQL Query

Parameterize a Query

Writing and Modifying

Insert, Update, or Merge

Delete Rows

Bulk Load Data

Create and Remove Tables

Use Transactions

Reference

Connector Node Settings

JDBC Driver Reference

Deprecated Node Mapping

Migrate Deprecated Workflows

Python

Overview

Tutorials

Python Scripting Quickstart

Data App Development Using Plotly

Data Processing

K-AI Scripting Assistant

Data Type Conversion

Batch Processing

Jupyter Integration

Environment Management

Pixi Configuration

Dependency Management

Environment Persistence

Channel Mirrors & Air-Gapped Setups

Conda Migration

Alternative Configurations

Conda and Miniforge Setup

Conda Environment Propagation

Manual Python Configuration

Legacy Node Migration

Concepts

Pixi Backend Architecture

Storage Logic

Python Environments on Executors

Reference

Python Scripting API

Bundled Packages

Executor and Hub Configuration

Troubleshooting Guide

API Reference

Inputs and outputs

Classes

Views

Utility functions

R

Deep Learning

Snowflake

Google Cloud

Azure

AWS

Big Data

Big Data Admin

Big Data Secured Cluster

Databricks

Microsoft Fabric

Power BI

Tableau

Report Designer

H2O

Changelogs

Version 5.12

Version 5.11

Version 5.10

Version 5.9

Version 5.8

Version 5.7

Version 5.6

Version 5.5

Version 5.3

Extensions

Add Packages to a Pixi or Conda Environment ​

This guide explains how to add Python packages to an existing environment, whether it is managed by Pixi (via the Python Environment Provider node) or by Conda.

Adding packages to a Pixi environment ​

The Python Environment Provider node allows you to manage dependencies directly within your workflow. You can specify which libraries your Python scripts will use using three different input modes.

  1. Double-click the Python Environment Provider node to open the configuration dialog.
  2. Select your preferred input mode to add packages:

Packages mode ​

This is the simplest way to add individual packages.

  1. In the Packages tab, click Add package.
  2. Type the name of the package (e.g., xgboost).
  3. (Optional) Specify a Min version and/or Max version to ensure compatibility.
  4. (Optional) Choose the Source for the package (e.g., Conda).

TOML editor ​

For more advanced users, you can specify channels and dependencies in TOML format:

toml
[workspace]
channels = ["knime", "conda-forge"]
platforms = ["win-64", "linux-64", "osx-64", "osx-arm64"]

[dependencies]
python = "3.14.*"
knime-python-base = "5.9.*"
plotly = ">=5.10"

YAML editor ​

Use a Conda-style YAML specification if you are migrating from an existing environment:

yaml
name: myenv
channels:
  - knime
  - conda-forge
dependencies:
  - python=3.14.*
  - knime-python-base=5.9.*
  - plotly>=5.10
  1. Click the Resolve Dependencies button. Pixi will check for compatibility and prepare the environment. If successful, you will see an Environment validated message with the status "Environment resolved successfully. Lock file generated."

  2. Click OK and re-execute the node. The environment will be updated (or recreated) with the new packages.

Adding packages to a Conda environment ​

If you manage your environment via Conda on the command line, install additional packages into an existing environment with:

bash
conda install --name my_python_env -c conda-forge <package>

For example:

bash
conda install --name my_python_env -c conda-forge xgboost=2.0

Further information on managing Conda packages can be found in the Conda documentation.

WARNING

Do not install the package knime using pip into the environment that will be used inside KNIME. This causes a name clash and makes importing knime.scripting.io fail. If you accidentally installed it, run pip uninstall knime in your Python environment.

Verifying the installed packages ​

After modifying the environment you can verify the installation:

  • Conda: conda list --name my_python_env
  • Inside a Python Script node: add import <package>; print(<package>.__version__) to your script, click Run all, and check the console output.

Next steps ​

  • Set up Pixi from scratch
  • Set up Conda / Miniforge
Pager
Previous pagePixi Configuration
Next pageEnvironment Persistence