Skip to content

Conversation

@xalelax
Copy link
Contributor

@xalelax xalelax commented Nov 3, 2025

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

@xalelax xalelax self-assigned this Nov 3, 2025
@codecov
Copy link

codecov bot commented Nov 3, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.42%. Comparing base (334a4e4) to head (1ca3223).

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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jpbrodrick89
Copy link
Contributor

jpbrodrick89 commented Nov 3, 2025

Why was our previous upper bound 3.12? Should we maybe not increment to 3.13 first? 😆

dionhaefner pushed a commit that referenced this pull request Nov 10, 2025
#### 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
@dionhaefner
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants