Skip to content

Add support for Python 3.13 #338

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add support for Python 3.13 #338

wants to merge 1 commit into from

Conversation

dstansby
Copy link

This adds support for Python 3.13, which was released a little while ago. I hope it's helpful - I'm happy to try and fix any issues found, or make any other changes needed.

The motivation here is to have wheels for Python 3.13 available.

@jmrouet
Copy link

jmrouet commented Apr 29, 2025

I would like also to upvote for this PR as binary wheels for blosc are not available on python 3.13.

I have created issue #339 that this PR should close.

who can approve this PR ?

@FrancescAlted
Copy link
Member

Thanks for the suggestion! Blosc 1.x series is not receiving any kind of funding for years, so it is in very low maintenance mode. We would like people to start using Blosc2, which is well more advanced and better funded. May I ask why you want to still use Blosc 1.x? In case you have compelling reasons for continuing using it, please consider funding the project; see Support Blosc for a Sustainable Future for details.

@jmrouet
Copy link

jmrouet commented Apr 29, 2025

Thanks very much for the reply.

We have an internal python package that depends on blosc 1.x, and we never tried to upgrade to blosc 2.
If it's the way to go rather than adding support for python 3.13 to blosc 1.x, we will investigate how to upgrade.

Are there any tutorials on how to upgrade from 1.x to 2 ?

@FrancescAlted
Copy link
Member

Great. We have tried hard to make Blosc2 API-compatible with Blosc1, so it should be easy. Mind that Blosc2 format is backward compatible with Blosc1, but the reverse is not true; this means that compressed data created with Blosc2 cannot be read with Blosc1-powered tools. Generally speaking, encouraging the transition to Blosc2 to your users is recommended.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants