feat(24.04): add python3 slice #387
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| package: python3 | ||
|
|
||
| essential: | ||
| - python3_copyright | ||
|
|
||
| slices: | ||
| core: | ||
| essential: | ||
| - python3.12_core | ||
|
|
||
| standard: | ||
| essential: | ||
| - python3.12_standard | ||
|
|
||
| utils: | ||
| essential: | ||
| - python3.12_utils | ||
| contents: | ||
| /usr/bin/pdb3: | ||
|
There was a problem hiding this comment. Do these files need to be symlinked to their python 3.12 alternatives in python3.12_utils? There was a problem hiding this comment. They are already symlinks when installed from python3 package, and they are linked properly (pdb3 linked to pdb3.12, etc). |
||
| /usr/bin/pydoc3: | ||
| /usr/bin/pygettext3: | ||
|
|
||
| copyright: | ||
| contents: | ||
| /usr/share/doc/python3/copyright: | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| summary: Integration tests for Python3 | ||
|
|
||
| environment: | ||
| SLICE/core: "core" | ||
| SLICE/standard: "standard" | ||
|
|
||
| execute: | | ||
| # Test different slice installations | ||
| echo "SLICE=${SLICE}" | ||
|
|
||
| rootfs="$(install-slices python3_${SLICE})" | ||
|
|
||
| cp ../python3.12/test_${SLICE}.py "${rootfs}/" | ||
| chroot "$rootfs" python3.12 /test_${SLICE}.py |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we modify or add a slice to link python3.12 to python3 and possibly python? Previously we would let the user link these, but If the user is simply including the python3 slice, it may prevent some confusion when migrating between python versions in different releases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A link from python to python3.12 is not created by the postinst script of python3 package, so I didn't include that in this slice. Besides, linking python3 to a specific python3.x version will cause conflicts when there are multiple python3.x packages in the same release (e.g. python3.10 and python3.11 in 22.04).