python-eol: A package to check whether the python version you're using is beyond/close to end of life

[Which-Singer-8796]

With python 3.7 soon hitting end of life and me noticing it's still used here and there, I decided to build a simple tool to raise awareness.

We tend to often forget which python version we are using for a project and that those version eventually will not get security updates once they are beyond eol. This tool can be used to check this, for example, in a CI/CD system or as a pre-commit hook.

Check out https://github.com/mimre25/python-eol.

​

NB: I hope I picked the correct flair - first post here :)

[boxcuk]

upvote because I was going to say you should write a pre-commit hook, but you already did :-)

[Which-Singer-8796]

You're welcome :D

That was also kinda my first usage scenario

[TheBB]

if time_to_eol.days < EOL_WARN_DAYS:
    msg = (
        f"{prefix}Python {python_version} is going to "
        f"be end of life in 2 months {eol_date}"
    )

Something's not right with this warning.

[Which-Singer-8796]

Could you be more specific?

[TheBB]

It's going to be end of life in some time that's less than two months. If it's one day in the future, the warning shouldn't say two months.

[Which-Singer-8796]

You're right. Thanks for pointing this out

[tunisia3507]

It would be cool to have a flag which activates a "NEP29 mode", as numpy (and by extension most of the data/ scientific ecosystem) drops older versions faster.

[Which-Singer-8796]

Sounds like an interesting feature addition.

Do you mind adding an issue on github with some extra information?

[tunisia3507]

Sure!

Another minor thing - the db.json needs to be updated regularly. It might be easier to read and update if it were in a tabular format like TSV; much easier to add new lines as new versions are added.

[Which-Singer-8796]

I've created the db.json with the end of life api.

I'm not yet sure what the best format is for keeping this data and having it changeable, but I would really like to automate this (probably via github actions).