fix(api): keep tokenizer loaders lazy at the public API boundary - #467
Open
chnlyy wants to merge 2 commits into
Open
fix(api): keep tokenizer loaders lazy at the public API boundary#467chnlyy wants to merge 2 commits into
chnlyy wants to merge 2 commits into
Conversation
Wrap load_tokenizer/load_processor lazily so importing areno.api / areno.api.trainer no longer pulls areno.engine.data.tokenizer. Extend the import-boundary CPU test to cover the seam and the engine tokenizer leak. Closes inclusionAI#65
chnlyy
force-pushed
the
fix/api-import-boundary
branch
from
August 11, 2026 11:03
f5763ef to
66f841b
Compare
chnlyy
changed the title
Author
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.
Wrap load_tokenizer/load_processor lazily so importing areno.api / areno.api.trainer no longer pulls areno.engine.data.tokenizer. Extend the import-boundary CPU test to cover the seam and the engine tokenizer leak.
Closes #65
What does this PR do?
Related issue
Fixes #(issue)
Type of change
How was it tested?
Checklist
pytest tests/ -k cpu).Breaking change details