Kedro is an open-source Python framework for creating reproducible, maintainable, and modular data science code. It applies software engineering best practices to data and analytics pipelines. The current version is 1.3.1, and releases are frequent, typically with patch and minor updates released monthly, and major versions less often.
pip install kedroVerified import paths — ran on the pinned version, not inferred.
This example demonstrates how to define Kedro nodes and combine them into a pipeline. It then uses a `SequentialRunner` and an in-memory `DataCatalog` to execute the pipeline. In a typical Kedro project, `kedro new` creates a project structure, and `kedro run` orchestrates execution via `KedroSession`, loading configurations from `conf/` files.
Upgrade your Python environment to 3.10 or a newer supported version.
Use `DataCatalog` instead of `KedroDataCatalog`. Review any custom catalog interactions for compatibility, especially error handling for missing datasets which now raise `DatasetNotFoundError`.
Always initialize new projects with `kedro new` and adhere to the generated project structure. When modifying configuration, follow the `conf/base` and `conf/local` conventions.
Use `params:` for values that are passed as inputs to node functions, often dynamic. Use `parameters:` for static, global configurations loaded via the `DataCatalog` and accessed from the `context.params` object or directly as dataset entries.
As of `kedro>=1.1.1`, only major version mismatches are strictly enforced. For older versions, ensure your project's `project_version` matches your installed Kedro package version. For new projects, ensure you're on a recent Kedro version to benefit from the more flexible version check.
Refactor pipelines to use modular pipeline features (`Pipeline(namespace=...)`) and explicit dataset naming conventions instead of relying on the deprecated `--namespace` flag.
Be aware that `@experimental` APIs are subject to change. Avoid using them in production code unless you are prepared to adapt to potential breaking changes in future releases.
Ensure your project's Python package structure is correct, remove any `.ipynb_checkpoints` folders from your `src` directory, and verify that the `register_pipelines` function in `src/<project_package>/pipeline_registry.py` accurately defines and returns your pipelines.
Add the `Scripts` directory of your Python environment (e.g., `C:\Users\Username\AppData\Roaming\Python\Python37\Scripts` or `<venv_path>\Scripts`) to your system's PATH. Alternatively, you can run Kedro commands by explicitly calling the Python module: `python -m kedro <command>`.
Navigate to the root directory of your Kedro project using `cd <your-kedro-project>` before attempting to run project-specific `kedro` commands.
Update your import statements and code to use `OmegaConfigLoader` instead of `ConfigLoader`. For example, change `from kedro.config import ConfigLoader` to `from kedro.config import OmegaConfigLoader`.