jupyter VS Kedro

6. Jupyter Jupyter is a collection of tools and applications designed for interactive computing and data visualization. At the heart of the Jupyter ecosystem is the Jupyter Notebook, an interactive web-based platform that allows you to create and share documents containing live code, equations, visualizations, and narrative text. It’s an excellent tool for exploratory data analysis, model prototyping, and creating reproducible data science workflows.

How cool. This motivated a quick search - this could be fun:

How to write your own kernel

https://jupyter-client.readthedocs.io/en/stable/kernels.html

All the language kernels (a lot of abandoned ones - the mariaDB one ('binder') will take a while to load but SQL in Jupyter!)

https://github.com/jupyter/jupyter/wiki/Jupyter-kernels

There are Jupyter kernels for Python, Mathics, Wolfram, R, Octave, Matlab, xeus-cling, allthekernels (the polyglot kernel). https://github.com/jupyter/jupyter/wiki/Jupyter-kernels

Not only there is. But it is only a simple Google search away... But to make it simpler... There are 3 😁 https://github.com/jupyter/jupyter/wiki/Jupyter-kernels

As it seems, this is not quite straight forward and manyusers have similar troubles.

Community maintained kernels : https://github.com/jupyter/jupyter/wiki/Jupyter-kernels

Derek Banas on YouTube is doing a "Python for Finance" course at ghe moment using Jupyter, and is making the files available. I believe he's done others too.Failing that, there's this Git repo: A gallery of interesting jupyter notebooks

Interesting, thanks for sharing. I'll definitely take a look, although at this point I am so comfortable with Snakemake, it is a bit hard to imagine what would convince me to move to another tool. But I like the idea of composable pipelines: I am building a tool (too early to share) that would allow to lay Snakemake pipelines on top of each other using semi-automatic data annotations similar to how it is done in kedro (https://github.com/kedro-org/kedro).

# pyproject.toml [project] dependencies = [ "kedro @ git+https://github.com/kedro-org/kedro@3ea7231", "kedro-datasets[pandas.CSVDataSet,polars.CSVDataSet] @ git+https://github.com/kedro-org/kedro-plugins@3b42fae#subdirectory=kedro-datasets", ]

So there's 2 sides to pipeline management: the actual definition of the pipelines (in code) and how/when/where you run them. Some tools like prefect or airflow do both of them at once, but for the actual pipeline definition I'm a fan of https://kedro.org. You can then use most available orchestrators to run those pipelines on whatever schedule and architecture you want.

We have set up a milestone on GitHub so you can check in on our progress and contribute if you want to. To suggest features to us, report bugs, or just see what we're working on right now, visit the Kedro projects on GitHub.

you could use a project framework like kedro to force you to be more disciplined about how you structure your projects. I'd also recommend checking out this book: Edna Ridge - Guerrilla Analytics: A Practical Approach to Working with Data

Recently I started a position as Developer Advocate for Kedro, an opinionated data science framework, and one of the things we're doing is exploring what are the best open source tools we can use to create our documentation.

You can also check out Kedro, it’s like the Flask for data science projects and helps apply clean code principles to data science code.

An often overlooked framework used by NASA among others is Kedro https://github.com/kedro-org/kedro. Kedro is probably the simplest set of abstractions for building pipelines but it doesn't attempt to kill Airflow. It even has an Airflow plugin that allows it to be used as a DSL for building Airflow pipelines or plug into whichever production orchestration system is needed.