-
Notifications
You must be signed in to change notification settings - Fork 293
[Setup] Python 3.11 alignment and cleanups #8981
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
| [project.optional-dependencies] | ||
| kfp = [ | ||
| "kfp~=1.8.22; python_version < '3.11'", | ||
| "kfp~=1.8.23; python_version >= '3.11'", | ||
| "kfp~=1.8.23", | ||
| ] |
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.
you bump the toml, need to bump the version as well
| [project] | ||
| name = "mlrun-pipelines-kfp-v1-8" | ||
| version = "0.5.8" | ||
| version = "0.5.9" |
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.
bump to 0.6
| [project] | ||
| name = "mlrun-pipelines-kfp-v2" | ||
| version = "0.5.3" | ||
| version = "0.5.4" |
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.
| version = "0.5.4" | |
| version = "0.6.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.
the change you are doing here is not a "patch" modification but rather a minor since we now dropping backwards compatibility support of python 3.9 - meaning, at least updating minor here.
adamdelman
left a comment
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.
Overall LGTM, minor comment.
### π Description Bump pipelines versions in requirements following the version bump done in : #8981 --- ### π οΈ Changes Made <!-- - Key changes (e.g., added feature X, refactored Y, fixed Z) --> --- ### β Checklist - [ ] I updated the documentation (if applicable) - [ ] I have tested the changes in this PR - [ ] I confirmed whether my changes are covered by system tests - [ ] If yes, I ran all relevant system tests and ensured they passed before submitting this PR - [ ] I updated existing system tests and/or added new ones if needed to cover my changes - [ ] If I introduced a deprecation: - [ ] I followed the [Deprecation Guidelines](./DEPRECATION.md) - [ ] I updated the relevant Jira ticket for documentation --- ### π§ͺ Testing <!-- - How it was tested (unit tests, manual, integration) --> <!-- - Any special cases covered. --> --- ### π References - Ticket link: Part of #8981 - Design docs links: - External links: --- ### π¨ Breaking Changes? - [ ] Yes (explain below) - [ ] No <!-- If yes, describe what needs to be changed downstream: --> --- ### ποΈ Additional Notes <!-- Anything else reviewers should know (follow-up tasks, known issues, affected areas etc.). --> <!-- ### πΈ Screenshots / Logs -->
π Description
This PR removes all remaining Python 3.9 support from the our codebase (following the PR: #8948 ).
π οΈ Changes Made
setup.pyand removing the Python 3.9 classifier.>=3.9, <3.12to>=3.11, <3.12StrEnumwith an alias to Python 3.11βs built-inenum.StrEnum_TDEngineColumnbecause the enum members hold _TDEngineColumnType objects not strings which StrEnum in Python 3.11 no longer accepts.β Checklist
π§ͺ Testing
Verified locally that installing MLRun under Python 3.9 fails as expected:
π References
π¨ Breaking Changes?
ποΈ Additional Notes