You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the Databricks platform, it is possible to use regular python modules in Repos and Workspaces.
It is even suggested by Databricks to use typical software engineering best practises. Here and here.
However, when using the Databricks CLI for importing files, especially a directory, into a Workspace by using databricks workspace import_dir, all .py files get automatically transformed to notebooks. This makes them incompatible because they cannot be imported as modules anymore.
The import and import_dir commands should probably only convert .py files starting with # Databricks notebook source to notebooks.
The text was updated successfully, but these errors were encountered:
cloudyday
changed the title
databricks workspace import(_dir) should not automatically convert .py files to notebooks
databricks workspace import(_dir) should not automatically convert non-notebook .py files to notebooks
Mar 20, 2023
On the Databricks platform, it is possible to use regular python modules in Repos and Workspaces.
It is even suggested by Databricks to use typical software engineering best practises. Here and here.
However, when using the Databricks CLI for importing files, especially a directory, into a Workspace by using
databricks workspace import_dir
, all .py files get automatically transformed to notebooks. This makes them incompatible because they cannot be imported as modules anymore.The import and import_dir commands should probably only convert .py files starting with
# Databricks notebook source
to notebooks.The text was updated successfully, but these errors were encountered: