[build] Upgrade py 3.10

[felixdittrich92]

This PR:

• Move to minimum py 3.10 for next release

• reason:

  • numpy 2.0 requires py >= 3.10
  • same for TF >=2.18 because it depends on numpy >= 2.0
  • same for onnxruntime >= 1.19 which dropped support for py 3.9 because of dep numpy >= 2.0

• Fix mypy

• minor numpy 2.0 compatibility fix int0 -> intp (does also exist in <2.0)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.59%. Comparing base (b411109) to head (ed7f468).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1770      +/-   ##
==========================================
+ Coverage   96.58%   96.59%   +0.01%     
==========================================
  Files         164      164              
  Lines        7895     7895              
==========================================
+ Hits         7625     7626       +1     
+ Misses        270      269       -1     

Flag	Coverage Δ
unittests	96.59% <100.00%> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[felixdittrich92]

@odulcy-mindee py3.9 end of life is Oct 25 but if already so many move to 3.10 i think we should follow that people will benefit from the improvements - Additional this would make it possible to move to python's built in types and away from the >= py3.11 deprecated typing types

[odulcy-mindee]

Why is there 3.11 written in this condition ?

[felixdittrich92]

It's still the action bug with macOS for the python matrix == 3.10 uses python 3.11 to avoid the bug do you remember ? :)

[odulcy-mindee]

Yeah, but why matrix.python == '3.10' && '3.11' || matrix.python ? Shouldn't matrix.os == 'macos-latest' && matrix.python == '3.10' be enough ?

[felixdittrich92]

@odulcy-mindee syntax is a bit confusing the last && defines which value to use so

matrix.os == 'macos-latest' && matrix.python == '3.10' -> if both True use 3.11 (&& '3.11') else use the matrix.python version

We could also used the version before so if macos-latest use always python 3.11 the change is a bit more explicit (but can be fully removed later on if we change to py 3.11 & py 3.12)

[felixdittrich92]

At the end with the current defined matrix.python array both commands does the same the change makes it only a bit more "fine grained" ^^

[odulcy-mindee]

Ah ok, thanks for the clarification

[felixdittrich92]

@odulcy-mindee you have to merge this (i can't ^^) and adjust the required test rules in the GitHub repo settings :)

[odulcy-mindee]

you have to merge this (i can't ^^) and adjust the required test rules in the GitHub repo settings :)

@felixdittrich92 done

[felixdittrich92]

Thanks 😊

[kuraga]

BTW, have **/__init__.py to be excluded?

[felixdittrich92]

Hey @kuraga :)

Yeah because it does strange things here:

init.py example:

from doctr.file_utils import is_tf_available, is_torch_available

if is_tf_available():
    from .tensorflow import *
elif is_torch_available():
    from .pytorch import *  # type: ignore[assignment]

and if i remember it has raised circular import issues on other places 😅

[kuraga]

Thanks :)