Support of python v3.10

[matthew-mizielinski]

According to the python developer's guide python 3.10 is supported until its end of life date of October 2026. Given that this package doesn't really use python, i.e. no impact on the code of the python version, would it be possible to extend the pyproject.toml to explicitly include this in the classifiers section?

[valeriupredoi]

@matthew-mizielinski my apologies for missing this one for so long, maintaining a fair number of packages has its pitfalls 😁 In the future, for anything maintenance in NCAS-CMS you can tag me right off the bat! We can turn on support for 3.10 since pyfive still supports it, but a lot of packages in conda forge are giving up support for it, so we may end up supporting it just in name. You folks at the MO are still using it, I should guess 🍺

[matthew-mizielinski]

@matthew-mizielinski my apologies for missing this one for so long, maintaining a fair number of packages has its pitfalls 😁 In the future, for anything maintenance in NCAS-CMS you can tag me right off the bat!

Will do

We can turn on support for 3.10 since pyfive still supports it, but a lot of packages in conda forge are giving up support for it, so we may end up supporting it just in name. You folks at the MO are still using it, I should guess 🍺

Thanks for picking this up and that would be good enough for us for now. We are still on python v3.10 for CDDS and will be updating before production runs start around Easter, but its a case of when do we have to do this relative to other tasks that need doing, e.g. adapting for new metadata standards and ensuring we can work with the new MASS archives.