fix(test): support tomli on Python 3.10 - #166
Merged
Merged
Conversation
sjy3
approved these changes
Aug 11, 2026
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
2 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.
Summary
Make the Harness Sidecar config tests use the standard-library
tomllibon Python 3.11+ and fall back to the SDKs already-declaredtomlidependency on Python 3.10.This changes test compatibility only. It does not change runtime dependencies, SDK behavior, wheel contents, tags, or publication state.
Failure fixed
The
v0.8.2Release to PyPI run failed during Python 3.10 test collection withModuleNotFoundError: No module named tomllib; Python 3.12 passed.Verification
Target config tests passed: 39/39.
The complete Harness Sidecar release subset passed on Python 3.12: 85/85.
Ruff check, Ruff format check, and
git diff --checkpassed. The PR matrix is expected to provide the exact Python 3.10 proof.Release note
The existing failed
v0.8.2tag is not changed by this PR. After merge, maintainers must explicitly choose whether to move that unpublished failed tag or release SDK 0.8.3.