Skip to content
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

Closed
tenzen-y opened this issue Mar 12, 2024 · 7 comments · Fixed by #2354
Closed

Define the Python deprecation/supporting policies for the Katib SDK #2283

tenzen-y opened this issue Mar 12, 2024 · 7 comments · Fixed by #2354

Comments

@tenzen-y
Copy link
Member

/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.

"Programming Language :: Python :: 3",
"Programming Language :: Python :: 3 :: Only",
"Programming Language :: Python :: 3.7",
"Programming Language :: Python :: 3.8",
"Programming Language :: Python :: 3.9",
"Programming Language :: Python :: 3.10",

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 👍

@tenzen-y
Copy link
Member Author

cc: @kubeflow/wg-automl-leads

@andreyvelich
Copy link
Member

@droctothorpe
Copy link
Contributor

I suggest either EOL or some small grace period after EOL just from a security perspective:
https://devguide.python.org/versions/

FWIW, pipelines still supports 3.7 😢 :
https://github.com/kubeflow/pipelines/blob/master/sdk/python/setup.py#L102

Copy link

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.

@tenzen-y
Copy link
Member Author

/remove-lifecycle stale

@andreyvelich
Copy link
Member

@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/ ?

@tenzen-y
Copy link
Member Author

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants