GH-51300: Fix deprecation warnings for null_placement - #51307
Open
taepper wants to merge 2 commits into
Open
Conversation
taepper
force-pushed
the
51300-deprecation-warning
branch
from
September 11, 2026 14:13
4c95a24 to
fb2250a
Compare
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.
Rationale for this change
Resolves #51300, which mentioned that deprecation warnings were being printed when executing the python tests.
What changes are included in this PR?
This migrates the test suite to use the non-deprecated api for
null_placementAre these changes tested?
Yes, python compute tests are still passing
Are there any user-facing changes?
No.