dev-python/pccm
Python C++ code manager (codegen used by cumm/spconv)
Screenshots
View
Download
BrowseChangeLog
commit d93be9d6ee886399a6fc5b338065f871a74926a1
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 14:26:19 2026 +0200
dev-python/pccm: declare the fire dependency
Upstream lists fire in install_requires unconditionally. It was omitted
here on the grounds that only the command-line path needs it, which is
true - __init__.py imports builder, core, middlewares and targets, and
upstream ships an empty console_scripts list, so nothing cumm or spconv
import at runtime reaches it.
That still leaves pccm/main.py installed while its module-level import
fire cannot resolve, so python -m pccm.main fails on a stock install.
dev-python/fire carries the same PYTHON_COMPAT, so declaring it costs no
Python targets.
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 62aea5971d06741a3aa936adda0aa1425a2287f3
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Jun 17 10:08:18 2026 +0200
dev-python/pccm: new package, add 0.4.16
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 14:26:19 2026 +0200
dev-python/pccm: declare the fire dependency
Upstream lists fire in install_requires unconditionally. It was omitted
here on the grounds that only the command-line path needs it, which is
true - __init__.py imports builder, core, middlewares and targets, and
upstream ships an empty console_scripts list, so nothing cumm or spconv
import at runtime reaches it.
That still leaves pccm/main.py installed while its module-level import
fire cannot resolve, so python -m pccm.main fails on a stock install.
dev-python/fire carries the same PYTHON_COMPAT, so declaring it costs no
Python targets.
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 62aea5971d06741a3aa936adda0aa1425a2287f3
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Jun 17 10:08:18 2026 +0200
dev-python/pccm: new package, add 0.4.16