[mlx_lm] Expose 'strict' parameter in load() function#1284
Open
zyguy wants to merge 1 commit into
Open
Conversation
This was referenced May 18, 2026
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.
Motivation: Currently, the high-level
mlx_lm.load()function does not expose thestrictparameter. This makes it impossible to passstrict=Falsewhen loading certain converted models or "abliterated" models that contain harmless orphaned weights.The underlying
load_model()function already supports thestrictargument. This PR simply surfaces it to the mainload()entrypoint, maintainingTrueas the default to ensure full backward compatibility. This will allow dependent projects likeoMLXto load a wider variety of fine-tuned or abliterated models without crashing.