emmatyping
Re:Python 3.15.0
on Friday October 09, 2026 @11:21AM (#50021799)
I clicked through some random ones which all worked, can you describe the ones that didn't work for you and how they failed?
Re:RISC-V is now officially supported by CPython
on Sunday August 30, 2026 @05:30AM (#49497089)
That's plausible. The bigger constraint to defaulting to RVA23 is that users are running on, and building all of their wheels targetting, RV64GC. So unless our users adopt RVA23, it would be unwise to switch.
Re:RISC-V is now officially supported by CPython
on Sunday August 30, 2026 @05:20AM (#49497039)
In short, we haven't found many bugs, but it also wasn't just recompile on a new platform.
We've seen test failures like https://github.com/python/cpython/issues/151040
And perf support needs to be tested and merged https://github.com/python/cpython/issues/121201
Overall though, fairly smooth sailing as you say.
The reason RISC-V wasn't already supported is a mix of lacking hardware access for build bots and committers willing to pledge time to support it.
Re:RISC-V is now officially supported by CPython
on Sunday August 30, 2026 @05:07AM (#49496988)
Speaking unofficially, opinions my own, etc.
We (CPython) currently only have access to RV64GC machines to test on, and so that is the defacto target we can currently support.
Personally, I hope to see RVA23 become the baseline in the future. But that will depend on adoption.
On the packaging side of things, the platform tag is manylinux_X_Y_riscv64. So far that has meant RV64GC. So before we set a baseline of RVA23, we will need to see where the community lands.