-
Notifications
You must be signed in to change notification settings - Fork 95
Breaking: Update sagemaker-training version >=5.0.0 #260
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
Changes from all commits
28d28e1
eba23ba
abdd2d1
45fa167
7f44b26
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1 @@ | ||
| 2.9.1.dev0 | ||
| 3.0.0 |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -25,7 +25,7 @@ def read(fname): | |
|
|
||
|
|
||
| test_dependencies = ['boto3', 'coverage==6.5.0', 'flake8', 'future', 'mock', 'pytest', 'pytest-cov', | ||
| 'pytest-xdist', 'sagemaker[local]<2', 'torch', 'torchvision', 'tox'] | ||
| 'pytest-xdist', 'sagemaker[local]', 'torch', 'torchvision', 'tox'] | ||
|
|
||
| setup( | ||
| name='sagemaker_pytorch_training', | ||
|
|
@@ -48,12 +48,11 @@ def read(fname): | |
| "Natural Language :: English", | ||
| "License :: OSI Approved :: Apache Software License", | ||
| "Programming Language :: Python", | ||
| 'Programming Language :: Python :: 3.7', | ||
| 'Programming Language :: Python :: 3.8', | ||
| 'Programming Language :: Python :: 3.9', | ||
| ], | ||
|
|
||
| install_requires=['retrying', 'sagemaker-training>=4.3.0,<=4.8.3', 'six>=1.12.0'], | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. do we need <6.0.0? if we keep version backward compatible, it will be good to always try to pull latest?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Given the base toolkit is now at v5, I don't think that it is a guarantee that we would not have a v6 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, I mean, shouldn't we keep base toolkit backward compatible so there's no restriction to upgrade to latest version even if we published V6?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I know what you mean, but for V5 our breaking release was not due to the base toolkit change itself, it was from a breaking dependency. Major version releases are for breaking non-backwards compatible changes. Otherwise if the change is backwards compatible that should come as a minor or patch release for the V5 major version |
||
| install_requires=['retrying', 'sagemaker-training>=5.0.0,<6.0.0', 'six>=1.12.0'], | ||
| extras_require={ | ||
| 'test': test_dependencies | ||
| }, | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.