-
Notifications
You must be signed in to change notification settings - Fork 442
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
Define the Python deprecation/supporting policies for the Katib SDK #2283
Comments
cc: @kubeflow/wg-automl-leads |
cc @kubeflow/wg-training-leads @droctothorpe @shipengcheng1230 @andreafehrman @harrisonfritz @kuizhiqing @yaobaiwei |
I suggest either EOL or some small grace period after EOL just from a security perspective: FWIW, pipelines still supports 3.7 😢 : |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
/remove-lifecycle stale |
@tenzen-y Should we just update our SDK readme to say that we are going to follow Python EOL cycle: https://devguide.python.org/versions/ ? |
SGTM |
/kind feature
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
As we discussed in #2278 (comment), currently, we support the following Python versions for the SDK, but we don't have any policies to decide which versions we should drop/support the Python version. So, we should define the Python deprecation/supporting policies for the SDK.
katib/sdk/python/v1beta1/setup.py
Lines 56 to 61 in 5837b8a
Additionally, I believe that it is possible to apply the same policies to the training-operator.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Appendix:
Love this feature? Give it a 👍 We prioritize the features with the most 👍
The text was updated successfully, but these errors were encountered: