-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix source version check #684
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/ao/684
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit b943bc1 with merge base 5998389 (): This comment was automatically generated by Dr. CI and updates every 15 minutes. |
maybe add these examples to tests? |
class TestTorchVersionAtLeast(unittest.TestCase): | ||
def test_torch_version_at_least(self): | ||
test_cases = [ | ||
("2.5.0a0+git9f17037", "2.5.0", True), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm confused, as I thought this should be False instead.
shouldn't 2.5.0a0 and 2.5.0.dev be <2.5.0 but >2.4?
I might misunderstand torch_version_at_least
usage though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Strictly speaking this is an internal only utility that we leverage in case torch makes certain breaking changes or adds new features upstream. So I can't think of many cases where we'd do one thing with 2.5 nightlies vs 2.5 official releases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
understood.
@msaroufim , when do you guys plan to make a new release? Is it monthly? |
We do monthly, next one branch cut is Sep 5 and release a few days later |
@crcrpar can you try this instead?
Fixes #679 (comment)
This just basically takes advantage of the fact that every PyTorch version has the format
X.Y.Z
and then some stuff