fix: pin transformers<5.13.0 to avoid AutoTokenizer.register breakage#1471
Open
rggammon wants to merge 1 commit into
Open
fix: pin transformers<5.13.0 to avoid AutoTokenizer.register breakage#1471rggammon wants to merge 1 commit into
rggammon wants to merge 1 commit into
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.
Problem
transformers==5.13.0 introduced a breaking change in AutoTokenizer.register() that causes mlx-lm to fail at import time with Python 3.14 on macOS.
The error occurs in mlx_lm/tokenizer_utils.py at:
python AutoTokenizer.register("NewlineTokenizer", fast_tokenizer_class=NewlineTokenizer)transformers 5.13.0 added a check in auto_factory.py that requires registered tokenizer classes to have module starting with 'transformers.'. Since NewlineTokenizer is defined in mlx-lm, not in transformers, this check fails.
Error:
To reproduce:
Fix
Pin transformers<5.13.0 as a temporary fix while a proper solution (e.g. updating the AutoTokenizer.register call to be compatible with the new API) is investigated.