Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Support Databrick Notebook (.py) <> Jupyter Notebook (.ipynb) conversion #977

Open
lukeSmth opened this issue Dec 14, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@lukeSmth
Copy link

lukeSmth commented Dec 14, 2023

The extension currently supports executing Databricks Notebooks in .py format interactively using VSCode's interactive window. An additional access mode could use jupytext and nbconvert to convert Databricks Notebooks to .ipynb. This conversion could be ephemeral, only existing while open the file is open in VSCode, or more permanent. In either case, changes to the .ipynb file could be synced with the .py file on save. The .ipynb could be added to the the user's .gitignore by default.

See the Jupytext for VSCode extension for an example. If a nbformat template for Databricks Notebook (.py) <> Jupyter Notebook (.ipynb) conversions was published and Jupytext for VSCode was updated to support custom formats then no further work would be needed.

The ideal state would be support within the Databricks VSCode extension and a published conversion template. The template would allow integration into the existing notebook conversion ecosystem.

@lukeSmth lukeSmth changed the title Support Databrick Notebook (.py) <> Jupyter Notebook (.ipynb) conversion [Feature] Support Databrick Notebook (.py) <> Jupyter Notebook (.ipynb) conversion Dec 14, 2023
@kartikgupta-db kartikgupta-db added the enhancement New feature or request label Apr 17, 2024
@MrTeale
Copy link

MrTeale commented May 2, 2024

+1 on this. This is actually one of the few blockers I have to developing solely in VSCode rather than the UI.

@kartikgupta-db - If you have a rough understanding of what would need to change for this to be implemented and would accept a PR, I'd be willing to have a go. Just need some guidance on getting started

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants