Add support for Python 3.14 - #607
Conversation
|
As for me, there is no rush in adding 3.14 in the test suite, all the more that the code doesn't need any adaptations. The resource consumption is not worth it IMO. |
|
This repo is pretty quiet and the extra CI time won't make much difference, but I'm fine to leave it until the beta if you prefer? |
|
Since you are the release manager for this and the next versions of Python, I see no issues to run it here. Any issues that arise Im sure will be smoothed out quickly 😜 |
|
Yes, and if we find any issues, it will help us get them fixed in CPython, or possibly other dependencies, before the big release in October. But again, I don't mind waiting a bit longer. |
|
Considering MS is building nuclear powerplants to power its infrastructure, I'd rather not push too much to add more compute power when there is no compelling added value ☢️ 😱 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #607 +/- ##
==========================================
+ Coverage 92.89% 93.01% +0.11%
==========================================
Files 28 28
Lines 3055 3105 +50
==========================================
+ Hits 2838 2888 +50
Misses 217 217 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Python 3.14 is now in beta and the release manager (👋 hi it's me!) requested:
https://discuss.python.org/t/python-3-14-0-beta-1-is-here/91117 Compute usage: this repo is fairly quiet, I think the benefits of making sure we're ready for 3.14 are greater than not testing it at all in CI. |
claudep
left a comment
There was a problem hiding this comment.
I guess that if we want to save some proc power, we could instead remove some intermediary Python versions. You have my blessing 👼
Python 3.14 is still in alpha, but I think we can start supporting it already?