Skip to content

Comments

add 3.13 support#495

Draft
mariostieriansys wants to merge 4 commits intomainfrom
mostieri/support_313
Draft

add 3.13 support#495
mariostieriansys wants to merge 4 commits intomainfrom
mostieri/support_313

Conversation

@mariostieriansys
Copy link
Collaborator

No description provided.

@codecov-commenter
Copy link

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.81%. Comparing base (b50b10f) to head (66f8c18).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #495   +/-   ##
=======================================
  Coverage   81.81%   81.81%           
=======================================
  Files          28       28           
  Lines        8144     8144           
  Branches     1496     1496           
=======================================
  Hits         6663     6663           
  Misses       1008     1008           
  Partials      473      473           

☔ 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.

@mariostieriansys mariostieriansys enabled auto-merge (squash) February 12, 2026 14:25
@viseshrp
Copy link
Collaborator

Hi @mariostieriansys. Thanks for this. We had to revert 3.13 support recently due to numpy in ADR. Please see here #475

Thanks

@viseshrp viseshrp disabled auto-merge February 12, 2026 14:41
@mariostieriansys
Copy link
Collaborator Author

Hi @mariostieriansys. Thanks for this. We had to revert 3.13 support recently due to numpy in ADR. Please see here #475

Thanks

On the new Python we are moving to numpy > 2, so I guess that'll help

@viseshrp
Copy link
Collaborator

@mariostieriansys
Actually, I think you were dealing with the same. Did you end up upgrading numpy in EnSight? We are still waiting on the team that builds numpy for EnSight Python to make a numpy 2.0+ release. Upgrading to 2 and above in pydyanmicreporting breaks compatibility in ADR.

@viseshrp
Copy link
Collaborator

viseshrp commented Feb 12, 2026

@mariostieriansys

Hi @mariostieriansys. Thanks for this. We had to revert 3.13 support recently due to numpy in ADR. Please see here #475
Thanks

On the new Python we are moving to numpy > 2, so I guess that'll help

Yes, we spoke to the team that builds numpy for the both of us. They said its not going to be available until April.

Indeed, the python contains an obscure build of numpy 2.0.0 which I don't know from where it comes from
So I am working with what we get from PyPi

@viseshrp viseshrp marked this pull request as draft February 12, 2026 16:39
@viseshrp viseshrp marked this pull request as ready for review February 12, 2026 17:07
viseshrp
viseshrp previously approved these changes Feb 12, 2026
@viseshrp viseshrp requested a review from margalva February 12, 2026 17:10
@viseshrp viseshrp linked an issue Feb 12, 2026 that may be closed by this pull request
@viseshrp viseshrp marked this pull request as draft February 17, 2026 19:37
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.

Numpy 2.X and Python 3.13 support

4 participants