Skip to content

Conversation

@Yacouby
Copy link
Member

@Yacouby Yacouby commented Nov 27, 2025

πŸ“ Description

This PR removes all remaining Python 3.9 support from the our codebase (following the PR: #8948 ).


πŸ› οΈ Changes Made

  • Dropped Python 3.9 support by requiring Python 3.11+ in setup.py and removing the Python 3.9 classifier.
  • Patch remote script: remove building and pushing of python 3.9 images.
  • Pipelines-adapters: updated the python requires constraint from >=3.9, <3.12 to >=3.11, <3.12
  • Replaced the custom StrEnum with an alias to Python 3.11’s built-in enum.StrEnum
  • Use Enum instead of StrEnum in _TDEngineColumn because the enum members hold _TDEngineColumnType objects not strings which StrEnum in Python 3.11 no longer accepts.

βœ… 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:

πŸ§ͺ Testing

Verified locally that installing MLRun under Python 3.9 fails as expected:

image

πŸ”— References


🚨 Breaking Changes?

  • Yes (explain below)
  • No

πŸ”οΈ Additional Notes

Comment on lines 18 to 21
[project.optional-dependencies]
kfp = [
"kfp~=1.8.22; python_version < '3.11'",
"kfp~=1.8.23; python_version >= '3.11'",
"kfp~=1.8.23",
]
Copy link
Member

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

@Yacouby Yacouby marked this pull request as ready for review November 30, 2025 08:37
@Yacouby Yacouby requested review from a team and adamdelman as code owners November 30, 2025 08:37
[project]
name = "mlrun-pipelines-kfp-v1-8"
version = "0.5.8"
version = "0.5.9"
Copy link
Member

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"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
version = "0.5.4"
version = "0.6.0"

Copy link
Member

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.

Copy link
Contributor

@adamdelman adamdelman left a 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.

@Yacouby Yacouby requested a review from Eyal-Danieli November 30, 2025 15:05
@liranbg liranbg merged commit 49378b4 into mlrun:development Dec 1, 2025
13 checks passed
@Yacouby Yacouby deleted the ML-11421 branch December 1, 2025 09:01
@Yacouby Yacouby mentioned this pull request Dec 1, 2025
10 tasks
liranbg pushed a commit that referenced this pull request Dec 1, 2025
### πŸ“ 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 -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants