Changing the default notebook file format from .ipynb to .py in Databricks has several implications based on current implementations and user scenarios:

1. User Experience: The .ipynb format captures more comprehensive data, including environment settings, visualizations, and widgets, enhancing user experience. In contrast, the .py format is more minimalistic, capturing only the source code

2. Compatibility Issues: There are potential concerns for users who primarily rely on Git and source control, as notebooks committed in the .py format may lack critical metadata and features compared to .ipynb files. This can lead to unexpected behavior, especially in serverless environments that utilize notebook features not captured in the source format

3. Impact on Existing Notebooks: Changing the default format will not retroactively affect existing notebooks. Only newly created notebooks will adopt the new default setting, ensuring that current workflows remain unaffected