Remove mlx upper version pin#4
Open
rromanchuk wants to merge 1 commit into
Open
Conversation
The <0.31 cap was added due to yolo26x-seg training hangs on mlx 0.31.x. Detection-only inference is unaffected; removing the cap so this package can be used alongside projects that require mlx>=0.31.
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 pin makes this project obsolete right out of the gate. It drives me bonkers when bleeding edge, high velocity frameworks get locked.
mlx>=0.30.3already signals that last version that worked, we can figure out the mlx regression on our own.For someone mlx training on yolo26x-seg on 0.31, a README.md note is plenty enough.