fix: #2863 lazy-load SQLiteSession exports#2864
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
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.
This pull request fixes package import failures in runtimes where Python's optional
sqlite3module is unavailable.It keeps
SQLiteSessionexported from bothagentsandagents.memory, but resolves it lazily so applications that only import core SDK symbols such asAgentandRunnerno longer import the SQLite backend. It also adds import-side-effect regression coverage that blockssqlite3/_sqlite3in a subprocess, verifies core imports still work, and confirms explicitSQLiteSessionimports still load the SQLite implementation.This pull request resolves #2863.