Skip to content

chore: bump python version #221

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

chore: bump python version #221

wants to merge 4 commits into from

Conversation

cosmic-chichu
Copy link
Contributor

update allowed python version

Signed-off-by: Shrivardhan Rao <[email protected]>
@cosmic-chichu cosmic-chichu self-assigned this Mar 27, 2025
Copy link

codecov bot commented Mar 27, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.20%. Comparing base (157a90d) to head (9694254).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #221   +/-   ##
=======================================
  Coverage   94.20%   94.20%           
=======================================
  Files          55       55           
  Lines        2311     2311           
  Branches      119      119           
=======================================
  Hits         2177     2177           
  Misses         97       97           
  Partials       37       37           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

pyproject.toml Outdated
@@ -21,7 +21,7 @@ classifiers = [
repository = "https://github.com/numaproj/numaflow-python"

[tool.poetry.dependencies]
python = ">=3.9, <3.13"
python = ">=3.9, <4.0"
Copy link
Member

Choose a reason for hiding this comment

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

Make it < 3.14.
Things might break otherwise in future

Copy link
Member

Choose a reason for hiding this comment

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

+1 Python changes a lot between the minor versions :)

Copy link
Member

Choose a reason for hiding this comment

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

TBH, it is very difficult to support 5 versions of Python simultaneously and have trouble free builds. I would vote for dropping support for 3.9 if we are adding 3.13.
Anyway 3.9 is going obsolete after Oct 2025.

Copy link
Member

Choose a reason for hiding this comment

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

+1 yank support for 3.9

Signed-off-by: Shrivardhan Rao <[email protected]>
@cosmic-chichu cosmic-chichu requested a review from ab93 March 27, 2025 16:49
Copy link
Member

@ab93 ab93 left a comment

Choose a reason for hiding this comment

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

Please make sure a minor version is released for this (when you release it).

@@ -21,7 +21,7 @@ classifiers = [
repository = "https://github.com/numaproj/numaflow-python"

[tool.poetry.dependencies]
python = ">=3.9, <3.13"
python = ">=3.9,<3.14"
Copy link
Member

@ab93 ab93 Mar 27, 2025

Choose a reason for hiding this comment

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

Add "Programming Language :: Python :: 3.13"
in the classifiers

Copy link
Member

Choose a reason for hiding this comment

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

You also need to add tests to make sure python 3.13 pass
https://github.com/numaproj/numaflow-python/blob/main/.github/workflows/run-tests.yml

Signed-off-by: Shrivardhan Rao <[email protected]>
@kohlisid
Copy link
Contributor

@cosmic-chichu

  1. Lets test the CI build workflow
  2. proto compatibility
  3. UDF e2e execution

@vigith
Copy link
Member

vigith commented Mar 27, 2025

  1. proto compatibility

This is tricky, let's a CI rule for that in a follow up. I do not want to block this PR because of that.

Signed-off-by: Shrivardhan Rao <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants