Update python to current supported versions. Also add experimental support for next python release

[Fale]

Description

Bump python version in the CI to current versions.

[Fale]

I've added back 3.9 and 3.10. Also I've pushed 3.12 to be ok to fail, since now it is failing. The best scenario would be to have up to 3.13 working properly, considering that 3.13 is already in Fedora 41 (released last month) and very soon other distros will move to it

[snejus]

I see that you're dropping support for Python 3.8 - note that this needs a bit more effort:

1. Looking through the release notes, checking the codebase against any removals/deprecations and updating the codebase accordingly.
2. Typing updates: we should use pyupgrade to align types used in the codebase with what Python 3.9 supports.
3. Update of Python constraints in the package.
4. Relevant updates in the documentation.
5. And finally the changelog note.

That's a couple of things just off the top of my head - there's likely a couple of others.

Are you happy to go ahead with the above or would you like to limit the scope of this PR to simply add support for the most recent version without removing Python 3.8?

[Fale]

I've added back 3.8.

The reason why I removed it in the first place was that it is EOL, but I don't mind it being there. The part I'm interested into is the support to the newest versions. I don't have anything against the old versions :).

[snejus]

Deps installation on Python 3.12+ seems to be failing due to numpy 1.24.4 which does not support Python 3.12. It added support in 1.26.0, however in the same release it also removed support for Python 3.8.

Poetry resolved this numpy version because we are still supporting Python 3.8. Just tried setting minimum python version to 3.9 in the package and resolved the dependencies - numpy indeed gets upgraded, which should resolve this issue.

I will shortly submit a PR that removes Python 3.8 support and fixes this issue for you.

[Fale]

Thanks a lot :)

As soon as the other PR is merged, I'll rebase this one :)

[snejus]

Thanks a lot :)

As soon as the other PR is merged, I'll rebase this one :)

I think you may be able to adjust the base branch for this PR to point to drop-py38 branch. Once that PR it's merged, the base will automatically reset to master.

[Fale]

Thanks! I've rebased on the drop-py38 branch. It now works properly on py3.12 but not yet with py3.13. I'm not sure if we want to move py3.13 to be ok to fail or you think it makes more sense to fix the compatibility to py3.13 directly