You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Priority for next release: Move to stable ABI!!! #240
With development slowing down, as most major issues have been tackled, releases become more scarce. This affects the ability to remain up to date with the latest python versions.
The latest python-isal on PyPI has seventy three build artifacts. This is untenable. It makes the release process tedious and long. Also the number of people who get annoyed the second a new stable CPYthon version is released and this library is not available increases. I'd rather do the updates at my own pace.
This will incur a performance cost given that _PyBytes_Resize cannot be used anymore and memory copying must be used. So be it. For larger blocks (where ISA-L really matters) it does not really matter.
Activity
rhpvorderman commentedon Nov 4, 2026
The latest python-isal on PyPI has seventy three build artifacts. This is untenable. It makes the release process tedious and long. Also the number of people who get annoyed the second a new stable CPYthon version is released and this library is not available increases. I'd rather do the updates at my own pace.
This will incur a performance cost given that
_PyBytes_Resizecannot be used anymore and memory copying must be used. So be it. For larger blocks (where ISA-L really matters) it does not really matter.[-]Move to stable ABI?[/-][+]Priority for next release: Move to stable ABI!!![/+]