Chore/drop py39 support

[aniketpati1121]

This PR drops Python 3.9 support in the Kubeflow Pipelines SDK and updates CI workflows
to run tests on Python 3.10. This ensures compatibility with upcoming Python versions
and keeps the SDK dependencies up-to-date.

[google-oss-prow]

Hi @aniketpati1121. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[github-actions]

🚫 This command cannot be processed. Only organization members or owners can use the commands.

[mprahl]

@aniketpati1121 it looks like your rebase with the latest master branch didn't come out cleanly. Could you please fix that so the commits from master aren't in your PR?

[aniketpati1121]

Hi @mprahl, I have resolved the rebase conflicts and updated the branch. All checks including DCO and CI have passed. The PR is now clean and ready for review.

[aniketpati1121]

Hi,
I have updated my branch chore/drop-py39-support and resolved all rebase conflicts.
All checks (DCO, CI) have passed.
Could you please review the PR and add /approve and /lgtm so it can be merged?
Thank you!

[aniketpati1121]

This PR removes unintended test files that were mistakenly included in the previous commits while dropping Python 3.9 support. The history has been cleaned up via rebase to ensure only relevant changes are retained.

Changes made:

Removed unintended test files (test_kfp_platformspec.py, test_kfp_version.py, and backup .save file).

Rebased commits to keep the PR clean and focused.

Added Signed-off-by to comply with the DCO requirement.

Next steps:

Awaiting workflow approval and review from maintainers.

[droctothorpe]

@aniketpati1121, first of all, thanks for the contribution! DCO is still not passing. You can see more details here.

Commit sha: [6976770](https://github.com/kubeflow/pipelines/pull/12176/commits/6976770b192160eba07879fd5c058a80fc0d1d09), Author: aniketpatil, Committer: aniketpatil; Expected "aniketpatil [[email protected]](mailto:[email protected])", but got "Aniket Patil [[email protected]](mailto:[email protected])".
Commit sha: [2d36eee](https://github.com/kubeflow/pipelines/pull/12176/commits/2d36eeec18b2a3ae6f1719eb682eb5ffb991336c), Author: aniketpatil, Committer: aniketpatil; Expected "aniketpatil [[email protected]](mailto:[email protected])", but got "Aniket Patil [[email protected]](mailto:[email protected])".

The email you signed the commits with is not the same as the email you signed the DCO with.

I'll kick off CI before you fix that. Please make sure to rebase as well. Thanks!

[droctothorpe]

/ok-to-test

[github-actions]

Approvals successfully granted for pending runs.

[droctothorpe]

Should we update the SDK reqs as well, not just CI?

• https://github.com/kubeflow/pipelines/blob/master/sdk/python/setup.py#L90
• https://github.com/kubeflow/pipelines/blob/master/sdk/python/setup.py#L101
• https://github.com/kubeflow/pipelines/blob/master/kubernetes_platform/python/setup.py#L75

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign mprahl for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• .github/OWNERS
• kubernetes_platform/OWNERS
• sdk/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[aniketpati1121]

Should we update the SDK reqs as well, not just CI?

• https://github.com/kubeflow/pipelines/blob/master/sdk/python/setup.py#L90
• https://github.com/kubeflow/pipelines/blob/master/sdk/python/setup.py#L101
• https://github.com/kubeflow/pipelines/blob/master/kubernetes_platform/python/setup.py#L75

Yes, thanks for pointing it out! I’ve updated both kubernetes_platform/python/setup.py and sdk/python/setup.py to drop Python 3.9 and adjust the python_requires field accordingly. The PR now reflects the changes for both the SDK requirements and the CI.

[droctothorpe]

Thanks, @aniketpati1121 ! Looks like you need to update some of the other workflows as well.