On 1/7/2026 16:35, Vincent Habchi wrote:
If I understand the documentation correctly, using python.versions in non py-*
ports results in mostly nothing. Only python.default_version seems to be
honoured.
My question is: wouldn’t it be sensible to automatically create variants based
on python.versions (e.g python.versions 314 315 → +python314 +python315
variants automatically generated), with a default version set to whatever
python.default_version binds to, so that the user would have a way to control
which python version every Python-dependent application member of the Python
portgroup uses, not just the py-* modules?
Ideally ports that use python and aren't modules that will be imported
by other python code should just use the current stable version. I'd
like to avoid further scope creep in the python portgroup, and I've
mentioned more than once in the past that it would be fine to add a new
portgroup to create these variants for the ports that want it, but
apparently so far nobody has found it worth the effort. That may be
because it only ends up being around 10 lines of code.
- Josh
