sci-ml/safetensors
Simple, safe way to store and distribute tensors
Screenshots
-
safetensors-9999~amd64test python_targets_python3_12 python_targets_python3_13 python_targets_python3_14 debug debug
View 
Download 
Browse License: Apache-2.0 Overlay: Miezhiko -
safetensors-0.8.0~amd64 ~arm64test python_targets_python3_12 python_targets_python3_13 python_targets_python3_14 debug debug
View Download Browse License: Apache-2.0 Overlay: stuff -
safetensors-0.8.0~amd64 ~arm64python_targets_python3_12 python_targets_python3_13 python_targets_python3_14 python_targets_python3_15 debug debug
View Download Browse License: Apache-2.0-with-LLVM-exceptions MIT Unicode-3.0 ZLIB Overlay: gentoo -
safetensors-0.7.0~amd64 ~arm64test python_targets_python3_11 python_targets_python3_12 python_targets_python3_13 python_targets_python3_14 debug debug
View Download Browse License: Apache-2.0 Overlay: gentoo
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 4035518667f9c6148a0391b78dcf166c1c522798
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat Jul 4 10:41:54 2026 +0200
sci-ml/safetensors: new package, add 0.8.0
Forked from ::gentoo (which ships 0.7.0) to carry 0.8.0 ahead of the main
tree: sci-ml/transformers 5.13.0 requires safetensors>=0.8.0, enforced at
import via a require_version assert.
CRATES regenerated from the 0.8.0 Cargo.lock (0.8.0 ships no lockfile, so
it was generated with cargo): pyo3 0.25 -> 0.28, plus objc2/rustix/tempfile/
windows-sys and others. RUST_MIN_VER raised to 1.85.0 (Cargo.toml declares
edition 2024, per the cargo eclass QA notice). Supersede when ::gentoo ships
0.8.0.
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 4035518667f9c6148a0391b78dcf166c1c522798
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat Jul 4 10:41:54 2026 +0200
sci-ml/safetensors: new package, add 0.8.0
Forked from ::gentoo (which ships 0.7.0) to carry 0.8.0 ahead of the main
tree: sci-ml/transformers 5.13.0 requires safetensors>=0.8.0, enforced at
import via a require_version assert.
CRATES regenerated from the 0.8.0 Cargo.lock (0.8.0 ships no lockfile, so
it was generated with cargo): pyo3 0.25 -> 0.28, plus objc2/rustix/tempfile/
windows-sys and others. RUST_MIN_VER raised to 1.85.0 (Cargo.toml declares
edition 2024, per the cargo eclass QA notice). Supersede when ::gentoo ships
0.8.0.