[MINOR] style(client-python): Apply black formatting - #12861
Open
laserninja wants to merge 1 commit into
Open
laserninja wants to merge 1 commit into
laserninja wants to merge 1 commit into
Conversation
Four files under clients/client-python are not formatted the way the pinned black version formats them, so the first unrelated change that touches them picks up incidental reformatting. The Gradle pythonFormat task reformats in place rather than checking, so CI stays green while the drift accumulates. Reformatting them now keeps future diffs focused. These are formatting-only changes; no behavior is affected.
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changes were proposed in this pull request?
This PR reformats four files under
clients/client-pythonwith theblackversion pinned inrequirements-dev.txt. The changes are line wrapping only; no behavior is affected.gravitino/api/catalog_change.pygravitino/api/file/fileset_change.pytests/integration/test_model_catalog.pytests/integration/test_relational_catalog.pyWhy are the changes needed?
These files are not formatted the way the pinned
blackversion formats them, so the next unrelated change that touches them picks up incidental reformatting in its diff.The drift is not caught today because the Gradle
pythonFormattask runsblackin place rather than in check mode, so CI stays green while the difference accumulates. Reformatting now keeps future diffs focused on their actual changes.I noticed this while working on the Semantic Model Python client sub-tasks and kept it out of those PRs.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Reformatted with the pinned
blackversion and confirmed a second run is a no-op, then ran the unit tests.