chore: bump python version

[cosmic-chichu]

update allowed python version

[codecov]

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.

[ab93]

Make it < 3.14.
Things might break otherwise in future

[vigith]

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

[ab93]

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.

[vigith]

+1 yank support for 3.9

[khneal]

Make it < 3.14.
Things might break otherwise in future

I'm against limiting the version of Python.
Please read the following: https://iscinumpy.dev/post/bound-version-constraints/
If you still think there's a good reason to block 3.14+, please share it.

Note that supported versions will still be listed in classifiers... so if somebody uses a version not listed, then they use at their own risk.

[khneal]

I'm ambivalent about dropping support for Python 3.9, so I'll refrain from giving an opinion on that.

[ab93]

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

[ab93]

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

[ab93]

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

[khneal]

Per my other comment, please consider changing to:

Suggested change

	python = ">=3.9,<3.14"
	python = "^3.9"

Or if none of this packages dependencies cap the Python version (unlikely), then this would be better:

Suggested change

	python = ">=3.9,<3.14"
	python = ">=3.9"

[kohlisid]

@cosmic-chichu

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

[vigith]

2. 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.

[khneal]

Please consider removing the Python minor version cap, maybe in the next PR.

Is this PR still moving forward? I don't see any updates more than a month, and Python 3.13 went GA more than 6 months ago.

[khneal]

Make it < 3.14.
Things might break otherwise in future

I'm against limiting the version of Python.
Please read the following: https://iscinumpy.dev/post/bound-version-constraints/
If you still think there's a good reason to block 3.14+, please share it.

Note that supported versions will still be listed in classifiers... so if somebody uses a version not listed, then they use at their own risk.

[khneal]

I'm ambivalent about dropping support for Python 3.9, so I'll refrain from giving an opinion on that.

[khneal]

Per my other comment, please consider changing to:

Suggested change

	python = ">=3.9,<3.14"
	python = "^3.9"

Or if none of this packages dependencies cap the Python version (unlikely), then this would be better:

Suggested change

	python = ">=3.9,<3.14"
	python = ">=3.9"