Migrate Python examples to Context Compiler 0.9 API - #62
Merged
Conversation
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
Migrates the Python example integrations to the Context Compiler 0.9 public API and updates the examples/tests to match the post-checkpoint architecture.
Why
The 0.9 API removed raw state access and continuation/checkpoint semantics. This branch updates examples to use the public engine boundary instead:
engine.premiseandengine.policiesfor semantic state accessDecisionhandlingexport_json()/import_json()for persistence where persistence is still part of the example0.2.0dev0integrationExample metadata
Checklist
Notes
Validation:
./scripts/validate_python.sh200 passed, 6 skipped(live tests)