Add Python 3.14 to the CI test Matrix

[dwskoog]

I merged streamz/master in and added a commit to include py314 in the test matrix.

[amotl]

Thank you. But wouldn't our repositories diverge, if we are cross-submitting GitHub PRs? Do you want me to merge this patch? Which option would you prefer? I am usually using rebase, or squash+rebase.

Because you have admin permissions on this repository when following the invite, feel free to merge at your disposal. Alternatively, I can just cherry-pick your commit into python-streamz#483 and close this PR again, so we will not get into bidirectional obstacles?

[dwskoog]

Thank you. But wouldn't our repositories diverge, if we are cross-submitting GitHub PRs? Do you want me to merge this patch? Which option would you prefer? I am usually using rebase, or squash+rebase.
Because you have admin permissions on this repository when following the invite, feel free to merge at your disposal. Alternatively, I can just cherry-pick your commit into python-streamz#483 and close this PR again, so we will not get into bidirectional obstacles?

I am avoiding opening a PR there to keep the python-streamz#483 discussion intact. However you want to pick this up is fine by me.

[dwskoog]

Closing this out since it's sorted now.

[amotl]

I think it's better keep the flow linear re. upstream vs. downstream vs. fork modes, instead of introducing a bidirectional flow between fork and upstream, or fork <-> fork.

• Add support for Python 3.14 python-streamz/streamz#483 (comment)

Did you know you can reference commits from all forks in discussions, they don't even need PRs to become visible to the whole network on GitHub. In this spirit, it's also easy to run a miniature collaborative workflow like:

Hey, I've staged an improvement to your patch. Feel free to cherry-pick 930c8be at your disposal.

[amotl]

Closing this out since it's sorted now.

Thank you so much for saving a few keystrokes on my end by completing python-streamz#483 excellently. I hope Martin will be happy about it. 🍀