Define the Python deprecation/supporting policies for the Katib SDK
tenzen-y opened this issue · 7 comments
/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:
- JupyterLab's policies: https://github.com/jupyterlab/jupyterlab/blob/main/pyproject.toml#L13
- Jupyter Server policies: https://github.com/jupyter-server/jupyter_server/blob/main/pyproject.toml#L24
Love this feature? Give it a 👍 We prioritize the features with the most 👍
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:
https://devguide.python.org/versions/
FWIW, pipelines still supports 3.7 😢 :
https://github.com/kubeflow/pipelines/blob/master/sdk/python/setup.py#L102