build

Relenv build is resposible for building Python and it’s dependencies from source. The build process also ensures Python is re-locatable. The directory containg the python build can be moved around on the filesystem or to another host machine of the same architecture.

relenv build

Options

Build Relenv Python Environments from source

usage: relenv build [-h] [--arch {x86_64,aarch64}] [--clean]
                    [--python {3.10.13,3.11.5}] [--no-cleanup]
                    [--force-download] [--step STEP] [--check-versions]

Named Arguments

--arch

Possible choices: x86_64, aarch64

The host architecture [default: “x86_64”]

Default: “x86_64”

--clean

Clean up before running the build. This option will remove the logs, src, build, and previous tarball.

Default: False

--python

Possible choices: 3.10.13, 3.11.5

The python version [default: “3.10.13”]

Default: “3.10.13”

--no-cleanup

By default the build directory is removed after the build tarball is created. Setting this option will leave the build directory in place.

Default: False

--force-download

Force downloading source tarballs even if they exist

Default: False

--step

A step to run alone, can use multiple of this argument. When this option is used to invoke builds, depenencies of the steps are ignored. This option should be used with care, as it’s easy to request a situation that has no chance of being succesful.

Default: []

--check-versions

Check for new version of python and it’s depenencies, then exit.

Default: False