Stop pinning an mlx-cv version in the model cards - #33
Merged
Conversation
Both cards told readers to install an exact version. That is a literal nobody remembers to touch: it sat at 0.0.3 through the 0.0.4 release, and the published cards on the Hub still say 0.0.3 today because they only update when someone manually re-uploads the weights. The pin was also wrong on its own terms. It froze readers on whatever version happened to be current when the weights were last pushed, so a reader arriving a year later installs a release that has since been fixed several times over. The install line carries no version now. The parity figures in each card's Verification section describe the checkpoint itself and do not move with the loader, so the card keeps its evidence without keeping a number that goes stale.
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.
Both cards told readers to install an exact version. That is a literal nobody remembers to touch: it sat at
0.0.3through the 0.0.4 release, and the published cards on the Hub still say 0.0.3 today, because they only update when someone manually re-uploads.The pin was also wrong on its own terms. It froze readers on whatever version happened to be current when the weights were last pushed, so a reader arriving a year later installs a release that has since been fixed several times over.
The install line carries no version now:
pip install "mlx-cv[mlx,hub]"The parity figures in each card's Verification section describe the checkpoint itself and do not move with the loader, so each card keeps its evidence without keeping a number that goes stale.
Publishing these to the Hub is a separate manual step and is being run alongside this change.