-
Notifications
You must be signed in to change notification settings - Fork 1
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
Python 3.13 launch issues #37
Comments
Note: We are currently only testing 3.12 in CI. Adopting nox and testing across 3.11 (min supported version) and 3.13 (currently release) would be recommended. edit: done in #43 |
Further observation: Testing in 3.13 produces: update: this is due to adtl importing pint, which is not 3.13 compliant yet, see globaldothealth/adtl#97 |
Python 3.13 tests fail in CI, see https://github.com/globaldothealth/InsightBoard/actions/runs/11261412066/job/31314794050?pr=44 in PR #44 as they cannot build pyarrow |
Added version compatiblity badges to alert the user while this issue is being resolved #47 |
Python 3.13 compatibility issues:
pyarrow does not build binaries for the platform (https://github.com/apache/arrow/issues/ 43519); because of this InsightBoard is taking a long time to install as it needs to build the binaries, and this appears to have caused an installation to fail on another machine (no logs available) where developer tools were likely not available. The pyarrow issue linked above states that v18 binaries for py3.13 are imminent and should resolve the problem.
Attempting to parse a file in 3.13 produces the error:
cannot inherit frozen dataclass from a non-frozen one
. This is actually not due toInsightBoard
, but due to theadtl
parser importingpint
, which is not 3.13 compliant yet (see Import error with Python 3.13 adtl#97).The text was updated successfully, but these errors were encountered: