Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python version in base images is out of date #9

Open
niloc132 opened this issue Feb 14, 2022 · 1 comment
Open

Python version in base images is out of date #9

niloc132 opened this issue Feb 14, 2022 · 1 comment
Assignees

Comments

@niloc132
Copy link
Member

The python version we get from debian since taking this approach to our images is down to 3.7.3, down from our previous 3.7.10 (latest is 3.7.13).

Ideally we should move back to 3.7.10 or something newer, and possibly track an upstream to ensure we stay up to date.

@devinrsmith
Copy link
Member

At the current time, we are using the apt package manager with a base image of debian:buster-slim. Granted, this isn't the latest version of debian, but I wish that they would keep python 3.7.x up-to-date with the latest patch releases.

It's likely a reasonable thing to assume our own responsibility for building and shipping the "correct" python version - in essence, trying to divorce our major components from the release cycles of upstream package managers. (The same argument can be made for java.)

If we do, we may choose to assume cpython build responsibilities (https://devguide.python.org/setup/), or use helper tools that essentially do the same thing (https://github.com/pyenv/pyenv/blob/master/plugins/python-build/README.md).

There may be a larger conversation to be had about the matrix of python versions we support, and if we want to change our base image.

@devinrsmith devinrsmith self-assigned this Feb 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants