Support Python 3.13 and drop Python 3.10 support. Create a new release once ready

[bobleesj]

To create a new release, follow the instructions in "Release Python package with GitHub Actions and tag" on GitLab. Simultaneously, in the "operation-release-everything" repository, cross off completed items under Phase 2. This process helps maintainers share and track progress.

[hakonanes]

Hi @bobleesj! You may have good reasons for dropping Python 3.10 support, but just note that NumPy will support it until April 2025, as stated in their support table.

[bobleesj]

@hakonanes Thanks for sharing the table! Allowing my supervisor here to share his thought @sbillinge

[sbillinge]

Thanks @hakonanes...yah, we are roughly working to NEP 29 deprecation_policy.html) which would mean supporting 3:10 until 18th Dec, but since it is mid October and we are but few, we thought we would do it at the same time now.....but if it is going to cause problems, please let us know. I need to check why numpy isn't following their own NEP on this.

[hakonanes]

No problem! Just curious. The argument about limited resources is always valid, and something we all struggle with... Thanks for answering.

[sbillinge]

for the record the code still works with 3.10 so we could remove that pin, it is just in the interests of good code hygiene in the wider stack that we want to follow the NEP (more or less :)