-
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
Conversation
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
| '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 comment
The 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?
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.
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 comment
The 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?
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 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
* Breaking: Update sagemaker-training version >=5.0.0 * update test dependency * Add latest version and python version to README * fix GitHub README shield badges * fix tests
Issue #, if available:
Description of changes:
sagemaker-training-toolkittosagemaker-training>=5.0.0,<6.0.0which includes breaking changesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.