Repository navigation
Document migration from the published 0.1.0 API - #7
Merged
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.
The actual 0.1.0 wheel on PyPI exposes a conversation-only Memory API, whereas the repository's pre-release code already used Context classes. The migration guide treated those as the same API and could mislead users upgrading the published package.
Document the constructor, add(), user namespace and result-format changes explicitly, distinguish repository users from PyPI users, and state that legacy tables are not imported automatically. Correct the Trusted Publisher instructions to add a publisher to the existing project.
Validated against the downloaded PyPI 0.1.0 wheel source. The existing 92 tests pass with branch coverage enabled (395/417 statements and 119/142 branches in pixelmemory). This is a documentation change; live provider calls and the CLIP model path remain outside that verification.