dev-python/omegaconf
Flexible YAML-based configuration system with variable interpolation
Screenshots
-
omegaconf-2.4.0_pre12~amd64python_targets_python3_12 python_targets_python3_13 python_targets_python3_14
View 
Download 
Browse License: BSD Overlay: stuff -
omegaconf-2.4.0-r4~amd64python_targets_python3_12 python_targets_python3_13 python_targets_python3_14
View Download Browse License: BSD Overlay: phackerlay
ChangeLog
commit d26e488d095396a8343a1053601f18f59982a8df
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 10:04:12 2026 +0200
*/*: drop dead Python targets from PYTHON_COMPAT
139 ebuilds across 65 packages still listed python3_10, python3_11 or
python3_13t. None of the three is a supported implementation any more:
gentoo's python-utils-r1 sets _PYTHON_ALL_IMPLS to python3_ plus
python3_t, and everything older falls into the branch commented
"implementations deprecated prior to EAPI 9 are fatal".
Inert today, which is why nothing caught it. Targets outside
_PYTHON_ALL_IMPLS are silently dropped rather than rejected, so they
never became USE flags and never produced a dependency atom -- an ebuild
declaring python3_ was only ever offering 12, 13 and 14.
Two reasons to clean them up anyway. The eclass branch they land in
dies for any EAPI other than 7 or 8, so all 139 are waiting to break on
the first EAPI 9 bump. And pkgcheck's OldPythonCompat is a git-scoped
check that only inspects ebuilds touched in a commit range, so it never
reports these on a full-tree scan and would instead fire on whichever
unrelated commit next touches one of them.
No revbump, because nothing observable changes. Verified on a sample
spanning every transformation shape that the python USE flags portage
offers are byte-identical before and after, and that a pkgcheck run
over all 65 packages returns a set-identical list of findings.
The eight python2_7 ebuilds are deliberately untouched: that target is
also absent from _PYTHON_ALL_IMPLS, but they reach it through the
_PYTHON_ALLOW_PY27 hatch in the overlay's forked python-utils-r1_py2.
commit 00310c85a2ce3a6a5e969519fe8a5cd88ff7fbfb
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat Jul 4 14:57:20 2026 +0200
dev-python/omegaconf: new package, add 2.4.0_pre12
YAML-based hierarchical config with variable interpolation, a dependency
of the LLaMA-Factory / HuggingFace training tooling. The 2.4 line is
chosen over the released 2.3.x deliberately: 2.3 pins the external
antlr4-python3-runtime to 4.9, whose ATN serialization is incompatible
with the 4.11 runtime the tree ships (deserialize raises "Could not
deserialize ATN with version 4"). 2.4 vendors its own ANTLR 4.11.1
runtime under omegaconf/vendor, so PyYAML is the sole external runtime
dependency.
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 10:04:12 2026 +0200
*/*: drop dead Python targets from PYTHON_COMPAT
139 ebuilds across 65 packages still listed python3_10, python3_11 or
python3_13t. None of the three is a supported implementation any more:
gentoo's python-utils-r1 sets _PYTHON_ALL_IMPLS to python3_ plus
python3_t, and everything older falls into the branch commented
"implementations deprecated prior to EAPI 9 are fatal".
Inert today, which is why nothing caught it. Targets outside
_PYTHON_ALL_IMPLS are silently dropped rather than rejected, so they
never became USE flags and never produced a dependency atom -- an ebuild
declaring python3_ was only ever offering 12, 13 and 14.
Two reasons to clean them up anyway. The eclass branch they land in
dies for any EAPI other than 7 or 8, so all 139 are waiting to break on
the first EAPI 9 bump. And pkgcheck's OldPythonCompat is a git-scoped
check that only inspects ebuilds touched in a commit range, so it never
reports these on a full-tree scan and would instead fire on whichever
unrelated commit next touches one of them.
No revbump, because nothing observable changes. Verified on a sample
spanning every transformation shape that the python USE flags portage
offers are byte-identical before and after, and that a pkgcheck run
over all 65 packages returns a set-identical list of findings.
The eight python2_7 ebuilds are deliberately untouched: that target is
also absent from _PYTHON_ALL_IMPLS, but they reach it through the
_PYTHON_ALLOW_PY27 hatch in the overlay's forked python-utils-r1_py2.
commit 00310c85a2ce3a6a5e969519fe8a5cd88ff7fbfb
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat Jul 4 14:57:20 2026 +0200
dev-python/omegaconf: new package, add 2.4.0_pre12
YAML-based hierarchical config with variable interpolation, a dependency
of the LLaMA-Factory / HuggingFace training tooling. The 2.4 line is
chosen over the released 2.3.x deliberately: 2.3 pins the external
antlr4-python3-runtime to 4.9, whose ATN serialization is incompatible
with the 4.11 runtime the tree ships (deserialize raises "Could not
deserialize ATN with version 4"). 2.4 vendors its own ANTLR 4.11.1
runtime under omegaconf/vendor, so PyYAML is the sole external runtime
dependency.