Uh oh!
There was an error while loading. Please reload this page.
[Python] Support non-experimental conf in Python code - #3539
Merged
Conversation
kanterovtemporarily deployed
to
test-trigger-is
September 2, 2025 13:56 — with 
GitHub Actions
Inactive
Collaborator
9 failing tests:
|
kanterov
marked this pull request as ready for review
September 2, 2025 14:52
kanterov
requested review from
andrewnester, anton-107, denik, pietern and shreyas-goenka
as code ownersSeptember 2, 2025 14:52
denik
reviewed
Sep 8, 2025
| return ( | ||
| _Conf(), | ||
| Diagnostics.create_error( | ||
| "Both 'python' and 'experimental/python' sections are present, use 'python' section only", |
Contributor
There was a problem hiding this comment.
Why not have validation in CLI itself and keep Python part light? E.g. use 'python', fallback to 'experimental.python'.
CollaboratorAuthor
There was a problem hiding this comment.
There is CLI validation in #3540, but we can't assume that both have the latest version. So we are defensive on both ends.
Contributor
There was a problem hiding this comment.
There is CLI validation in #3540, but we can't assume that both have the latest version.
Why not enforce minimum or exact databricks-bundles version in CLI?
CollaboratorAuthor
There was a problem hiding this comment.
This change is also ready to go now. We don't need to wait for the CLI release including support for non-experimental "python" section
Contributor
There was a problem hiding this comment.
For discussion: do you have ideas on how to enforce bidirectional compat for future changes? If so, do we use some kind of version range to do this? Some changes will require a coupled bump. It may be easier to just require version coupling, or at least warn if you're using different versions.
pietern
approved these changes
Sep 8, 2025
pietern
left a comment
Contributor
There was a problem hiding this comment.
The change itself looks good.
Let's continue the discussion about the merits of version checks elsewhere.
Uh oh!
There was an error while loading. Please reload this page.
pietern pushed a commit
that referenced
this pull request
Oct 27, 2025
## Changes Move `python` outside of the `experimental` section. The change is backward-compatible and forward-compatible. If CLI is using a newer or older version of `databricks-bundles,` it will continue to work. It's implemented by copying the content of `python` into `experimental.python`. If we don't offer compatibility, there is a risk that previously deployed resources will be erased because we wouldn't be able to load resources. See also #3539 ## Why Python support for Databricks Asset Bundles is graduating from the experimental status. ## Tests Acceptance tests check that previous `databricks-bundles` versions continue to work.
denik pushed a commit
that referenced
this pull request
May 20, 2026
## Changes Support reading both `python` and `experimental.python` configs. If both are set, their value should be equivalent. After we introduce the `python` section into the CLI, it has to keep setting both `python` and `experimental.python` into the payload for backward compatibility. After that, Python code can start erroring out if `experimental/python` is set but not `python` because it means that users have an outdated CLI version. See also #3540 ## Why It's a step toward graduating `python` outside the `experimental` section. ## Tests Unit tests and existing acceptance tests
denik pushed a commit
that referenced
this pull request
May 20, 2026
## Changes Move `python` outside of the `experimental` section. The change is backward-compatible and forward-compatible. If CLI is using a newer or older version of `databricks-bundles,` it will continue to work. It's implemented by copying the content of `python` into `experimental.python`. If we don't offer compatibility, there is a risk that previously deployed resources will be erased because we wouldn't be able to load resources. See also #3539 ## Why Python support for Databricks Asset Bundles is graduating from the experimental status. ## Tests Acceptance tests check that previous `databricks-bundles` versions continue to work.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Support reading both
pythonandexperimental.pythonconfigs. If both are set, their value should be equivalent.After we introduce the
pythonsection into the CLI, it has to keep setting bothpythonandexperimental.pythoninto the payload for backward compatibility. After that, Python code can start erroring out ifexperimental/pythonis set but notpythonbecause it means that users have an outdated CLI version.See also #3540
Why
It's a step toward graduating
pythonoutside theexperimentalsection.Tests
Unit tests and existing acceptance tests