Python 3.8 EOL

[frack113]

https://devguide.python.org/versions/

As 3.8 is finally at the end of life, I remove it

Did NOT edit the release.yml :

• actions/setup-python@v4 -> v5
• python-version: 3.8 -> 3.9 ?

Test faild with Python 3.13, I haven't dug yet

[thomaspatzke]

Still struggling on this:

• Pro: no dependency on EOL Pythons.
• Pro: new features can be used. There were several occasions where I wrote less nice code just for the 3.8 compatibility. These could now be rewritten. Sticking on old Pythons would block progress.
• Against: Lots of stuff depends on EOL Pythons, e.g. Ubuntu LTS like 20.04 (but newer installable), Splunk (lost anyways, they use 3.7!).

I tend to Pro and merge. What do you think?

[branchvincent]

fyi #289 presumably fixes the 3.13 test failures

[frack113]

Hi,
for splunk "Beginning in Splunk Enterprise version 9.3, Splunk supports Python version 3.9 by default."
If we keep 3.8, we'll have to keep the other unsupported stuff, because an editor won't make the effort.
I'm more in favor of making the effort to be compatible 3.9 to 3.13

[thomaspatzke]

Ok, let's do it this way!

[thomaspatzke]

Can you also change the deployment/publish flow to a newer one?

[frack113]

Can be Squash and merge, too many commit to make a simple change 😄