tablib
tablib copied to clipboard
Add support for Python 3.14
Python 3.14 is still in alpha, but I think we can start supporting it already?
- https://devguide.python.org/versions/
- https://peps.python.org/pep-0745/
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 :radioactive: :scream:
Codecov Report
:white_check_mark: All modified and coverable lines are covered by tests.
:white_check_mark: Project coverage is 93.01%. Comparing base (dcab406) to head (9f944f6).
:warning: Report is 18 commits behind head on master.
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
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
Python 3.14 is now in beta and the release manager (👋 hi it's me!) requested:
We strongly encourage maintainers of third-party Python projects to test with 3.14 during the beta phase and report issues found to the Python bug tracker as soon as possible. While the release is planned to be feature-complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (Tuesday 2025-07-22). Our goal is to have no ABI changes after beta 4 and as few code changes as possible after the first release candidate. To achieve that, it will be extremely important to get as much exposure for 3.14 as possible during the beta phase.
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.