-
Notifications
You must be signed in to change notification settings - Fork 4
Bump python version in ci #388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #388 +/- ##
==========================================
- Coverage 76.35% 71.42% -4.94%
==========================================
Files 29 29
Lines 3346 3346
Branches 525 525
==========================================
- Hits 2555 2390 -165
- Misses 558 758 +200
+ Partials 233 198 -35 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Why was our previous upper bound 3.12? Should we maybe not increment to 3.13 first? 😆 |
#### Relevant issue or PR The docs build CI was failing because `setup-python` with `python-version-file: "pyproject.toml"` selects the latest available Python version (3.14), which is incompatible with PyO3 v0.24.0 used by pydantic-core. #### Description of changes Bound python to <3.14 until we finalize #388 and add official 3.14 support. #### Testing done CI
|
Got a few incompatibilities still, and a resource warning from SQLite3 (I assume via MLFlow) that seems benign and safe to ignore. More information:
Most importantly, all of those are related to testing specifically so users should already be able to run Tesseract Core with Python3.14. |
Relevant issue or PR
Tests ran only up to python 3.13, we should test on 3.14 as well
Description of changes
Testing done