feat: add Python 3.14 - #5206
Conversation
|
Hi @rettinghaus , thanks for opening this PR. We're definitely keen to add python 3.14 support across the Kedro ecosystem. Are you still interested in finishing this? |
|
Yes, what needs to be done? |
|
Thanks @rettinghaus ! It looks like right now the unit tests are failing for 3.14. We have guidelines that describe how to run the tests locally. Let me know if you need any help. |
11e0c24 to
f22eb22
Compare
Signed-off-by: rettinghaus <klaus.rettinghaus@gmail.com>
Signed-off-by: rettinghaus <klaus.rettinghaus@gmail.com>
|
Hi @rettinghaus 👋 I noticed that some tests are failing for Python 3.14 in this PR. Are you planning to continue working on fixing them, or would you like some help to get them passing? Either way works - just wanted to check so we know how to proceed. Thanks! |
|
Sorry, I lost track of this. Any help would be appreciated. Thanks. |
No worries! One of our team members will help to finalise it 🙂 |
|
closing this for now in response to #5511 |
Description
Adding Python 3.14 to the CI.
Development notes
Developer Certificate of Origin
We need all contributions to comply with the Developer Certificate of Origin (DCO). All commits must be signed off by including a
Signed-off-byline in the commit message. See our wiki for guidance.If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.
Checklist
RELEASE.mdfile