Hi @channel , we are excited to announce the Kedro...
# announcements
n
Hi @channel , we are excited to announce the Kedro 0.19.8 release today! 📣 Say bye to the good old
databricks_run.py
. Kedro projects now come with a single entrypoint that supports the full Kedro CLI even in interactive environments such as Databricks. This means you can do
python -m <package_name> run
anywhere. Checkout our updated 🧱 Databricks deployment docs for more details. 🚀 Major features and improvements • Made default run entrypoint in
__main__.py
work in interactive environments such as IPython and Databricks. 🪲 Bug fixes and other changes • Fixed a bug that caused tracebacks disappeared from CLI runs. • Moved
_find_run_command()
and
_find_run_command_in_plugins()
from
__main__.py
in the project template to the framework itself. • Fixed a bug where
%load_node
breaks with multi-lines import statements. • Fixed a regression where
rich
mark up logs stop showing since 0.19.7. ✍🏼 Documentation changes • Add clarifications in docs explaining how runtime parameter resolution works. Read the complete release notes for kedro on GitHub Thanks a lot to our community contributors: • cclausseltociearltalirz We welcome every community contribution, large or small. See what we're working on now and report bugs or suggest future features. Until next time, The Kedro Team 💛
❤️ 6
🧱 1
K 3
y
@Richard Purvis first paragraph may be relevant, FYI
n
@Jens Peder Meldgaard This should make
kedro-databricks
easier to work with. The entrypoint now support full kedro run arguments
❤️ 2
r
Very excited to implement this! The databricks developer experience with Kedro keeps getting better.
❤️ 2
🥳 1