Clarify backwards compatibility policy

Open
#964 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, python
Domain
documentation

Research direction

Begin by reading issue #954 and the existing discussion on this issue. The payload names no file, test, or entry point; the work is complete when the compatibility policy for Python images, image version locking, and security-update expectations is decided and documented.

Written by the indexing model from the issue text.

Description

As of #954 setuptools was completely removed from the python3.12+ base images, which is not the kinda of change I would have expected from this version.

It would be helpful to have some clarifications on what kinda of changes to expect from the images, and if there are versions of the image that are locked or will be locked so we can update them without risk of breaking everything and still get security updates.

Dominant language
Dockerfile
Stars
2.8k
Forks
1.1k
Avg merge
3d 1h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docker-library/python

All issues in docker-library/python

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.