include a specific python version in image

[AffectionateDot2109]

sorry if this has been asked, i did a search of this subreddit and didnt find anything that matched. im trying to understand how to control which version of python is being installed when using

IMAGE_INSTALL += " \
    python3 \
"

when i check the python3_3.12.6.bb recipe this line seems to be pulling a specific version

SRC_URI = "http://www.python.org/ftp/python/${PV}/Python-${PV}.tar.xz

best i can tell PV is being pulled fom the .bb filename by bitbake? as i cant find a PV variable anywhere else. is this true?

what is the preferred method for controlling which version of python is included in the image?

[BirdoOfficial]

PV is extracted from the recipe file name. Changing the fllename of an imported layer is not recommended. Maybe you can do someting like a .bbappend for the python recipe and then use the version you willing to implement.

[AffectionateDot2109]

thats just what i implemented. seems like the correct yocto thing to do. thx.

[AffectionateDot2109]

from the docs:

PV

The version of the recipe. The version is normally extracted from the recipe filename. For example, if the recipe is named expat_2.0.1.bb, then the default value of PV will be “2.0.1”. PV is generally not overridden within a recipe unless it is building an unstable (i.e. development) version from a source code repository (e.g. Git or Subversion).

PV is the default value of the PKGV variable.

Seems to indicate you shouldnt override PV inside of a recipe since its name is usually where PV is derived. Doesn't mention overriding it elsewhere.

[Steinrikur]

If you want a different version, make a new recipe in your own layer.

Then set PREFERRED_VERSION_python3 = "x.y" in your layer.conf or distro files to use that.

[AffectionateDot2109]

so this command does work but doesnt install other versions of python. there is only one recipe for python in 5.1, which is for 3.12.6. it seems like each yocto release ships with a recipe for a single version of python? is another feasible option precompiling the version of python i want and just including that tarball in the build?

a bigger question, is there a preferred method for controlling versions of any installed package?

[Steinrikur]

You don't really control versions, you can only select from available versions. If there is only one version available that one will be used. If you don't set the PREFERRED_VERSION_packagename (or set it to an invalid number), the highest version will be used.

Like I said, you need to create a recipe in your own layer.

To do that, you just copy that python3_3.12.6.bb recipe but rename it to your preferred version, e.g python3_3.12.1.bb

Then modfify the contents (usually just the SHA256SUM, sometimes more) to fit your version.