Add support for python 3.13

[jlaehne]

A few sentences and/or a bulleted list to describe and motivate the change:

• Add support for python 3.13
• Drop support for python 3.8
• Test for oldest supported hyperspy version and pin to >=v1.7.3

Progress of the PR

• Change implemented (can be split into several points),
• add a changelog entry in the upcoming_changes folder (see upcoming_changes/README.rst),
• Check formatting of the changelog entry (and eventual user guide changes) in the docs/readthedocs.org:lumispy build of this PR (link in github checks),
• ready for review.
• Test 3.13 against hs-RnMinor as Python 3.13 hyperspy/hyperspy#3468 is not yet released

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.30%. Comparing base (098b669) to head (39e471b).
Report is 7 commits behind head on main.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #225   +/-   ##
=======================================
  Coverage   99.30%   99.30%           
=======================================
  Files          12       12           
  Lines         576      576           
=======================================
  Hits          572      572           
  Misses          4        4           

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

[ericpre]

Would it be worth dropping python 3.8 support? It is not supported officially anymore: https://devguide.python.org/versions

[jlaehne]

Would it be worth dropping python 3.8 support? It is not supported officially anymore: https://devguide.python.org/versions

Valid point, I was wondering how far backwards to still support python versions when still supporting hyperspy 1.7.x

The multiple tests were just temporary for the moment to see which minor version of 1.7 ist still supported.

[jlaehne]

@ericpre do you have a spontaneous idea why the 3.13 tests give an event trigger failure when a signal/axes object is part of a touple of possible test inputs?

[ericpre]

Yes, it needs hyperspy/hyperspy#3468 to be released!