[codex] Add generated SDK import smoke test#60
Closed
ivanleomk wants to merge 1 commit into
Closed
Conversation
Author
|
Superseded by #61 from branch import-smoke-test. |
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
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
Adds a lightweight unittest smoke test for generated SDK import integrity.
The test verifies that:
import kagglesdksucceedskagglesdk.*module imports cleanlyKaggleClient()instantiates*_clientsubclientsWhy
The 0.1.31/0.1.32 import regression was caused by generated files referencing modules that were not included in the synced/published package. A build-only release step can still succeed in that case because wheel construction does not import the full transitive module graph.
This gives the release flow a cheap import-closure check that catches missing generated modules before publishing.
Evidence
Current
mainplus this test fails in a fresh Python 3.13 venv afterpip install -e .:The same test overlaid onto
origin/fix-imports-0.1.33passes in a fresh Python 3.13 venv afterpip install -e .:Commands used:
/opt/homebrew/bin/python3 -m venv .venv .venv/bin/python -m pip install -q --upgrade pip .venv/bin/python -m pip install -q -e . .venv/bin/python -m unittest tests.test_import_smoke