On 29/06/2026 11:07 am, Vincent Habchi wrote:
By the way Josh, I don’t mean to harass you, but I’m having a hard time
understanding how the default python version works if not explicitly specified
in a Portfile.
Namely, I would expect the Python select mechanism to default on the version
chosen manually by python_select or python3_select. But in the Python
Portgroup, the relevant function looks like this:
proc python_get_default_version {} {
global python.versions
set def_v 314
if {[info exists python.versions] && ${def_v} ni ${python.versions}} {
return [lindex ${python.versions} end]
} else {
return ${def_v}
}
}
Why is 314 hardcoded in this?
Vincent
In the interest of reproducible builds, builds intentionally ignore your
private python selection choices. Having builds run without random
python version a user might have selected, via their PATH, would be a
nightmare.
Chris
