Re-apply creation of python-3.12-base. #14943
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We tried python-3.12-default to provide symlinks python3 -> python3.12. That caused some problems as many things expected to get a /usr/bin/python3 (or /usr/bin/python) from installing 'python-3.12'.
The change here is to instead have python-3.12 provide /usr/bin/python3 as it did before, and depend on python-3.12-base for the primary files. python-3.12 and python-3.12-dev contain only symlinks.
The other changes here are a move of some files out of the runtime package and into -dev (usr/lib/python3.X/config-3.X-x86_64-linux-gnu). debian/ubuntu put these files in the -dev package.
Fixes:
Related:
Pre-review Checklist
For new package PRs only
endoflife.date)For new version streams
name: ${{package.name}}-compat)provides:logical unversioned forms of the package (e.g.nodejs,nodejs-lts)For security-related PRs
For version bump PRs
epochfield is reset to 0For PRs that add patches