dev-python/beanquery
Customizable lightweight SQL query tool for Beancount (BQL)
Screenshots
View
Download
BrowseChangeLog
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 8c1f4d059d1a431135d3dedce21ff4601d483705
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jun 16 16:41:03 2026 +0200
dev-python/beanquery: Keyword 0.2.0 for ~arm64
Pure-Python (PEP517), architecture-independent.
commit f333eb6f8b11784a22cd982285aaea9b10499e93
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jun 2 19:17:14 2026 +0200
dev-python/beanquery: deselect render tests stale vs beancount 3.2.3
beancount 3.2.x reserves a leading sign-alignment column, so rendered amounts
gain a space that 0.2.0's width-exact query_render assertions predate. The
renderer is correct (verified end-to-end) and 0.2.0 is latest; deselect with
a dated note.
commit 8c6d243b69c5c5a8b454fca9e47bcd35fec44f24
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jun 2 19:17:14 2026 +0200
dev-python/beanquery: new package, add 0.2.0
Beancount 3's BQL query engine (bean-query), split from the v2 monolith;
pulls in tatsu-lts. Same stray-top-level fix as beangulp: scope discovery to
beanquery* (find={} sweeps docs/).
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 8c1f4d059d1a431135d3dedce21ff4601d483705
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jun 16 16:41:03 2026 +0200
dev-python/beanquery: Keyword 0.2.0 for ~arm64
Pure-Python (PEP517), architecture-independent.
commit f333eb6f8b11784a22cd982285aaea9b10499e93
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jun 2 19:17:14 2026 +0200
dev-python/beanquery: deselect render tests stale vs beancount 3.2.3
beancount 3.2.x reserves a leading sign-alignment column, so rendered amounts
gain a space that 0.2.0's width-exact query_render assertions predate. The
renderer is correct (verified end-to-end) and 0.2.0 is latest; deselect with
a dated note.
commit 8c6d243b69c5c5a8b454fca9e47bcd35fec44f24
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jun 2 19:17:14 2026 +0200
dev-python/beanquery: new package, add 0.2.0
Beancount 3's BQL query engine (bean-query), split from the v2 monolith;
pulls in tatsu-lts. Same stray-top-level fix as beangulp: scope discovery to
beanquery* (find={} sweeps docs/).