Feature Request: Python Version Tags

[adamzr]

Python libraries are frequently incompatible with new Python minor versions. For example, many of my projects will break if switched today to Python 3.12 as they use libraries that only support Python 3.11. I would like to use distroless, but I can't have all my projects break on the day that distroless decides to switch from Python 3.11 to Python 3.12 (or the day the Debian updates). Please create tags or separate images for Python 3.8 through Python 3.12 that will always use the latest patched versions of those versions.

Thank you!

[axiomofjoy]

Out of curiosity, when will distroless move to Python 3.12?

[chulkilee]

It would even better to specify the patch version (e.g. 3.11.9 instead of 3.11) to prevent from having version differences between local dev/test vs production in container.

Also it's cumbersome to check the actual python version from distroless images.

We can keep the backward compatibility by keeping the current tags.

[gms1]

You can expect that the Python versions included in the gcr.io/distroless/python3-debian11, gcr.io/distroless/python3-debian12 and the next gcr.io/distroless/python3-debian13 image are different, but there will never be a version change in one of these images, so such a tag would never change