Skip to content
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

Updated cibuildwheel to 2.22.0 #14

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Conversation

SfinxCZ
Copy link
Contributor

@SfinxCZ SfinxCZ commented Feb 6, 2025

  • updated cibuildwheel to 2.22.0 (python 3.13 support)
  • enabled freethreading support (experimental)

- enabled freethreading support
@alesanfra
Copy link
Owner

Hi @SfinxCZ, thank you for contributing this PR. It looks like there are 3 broken builds, and I'd like to have them fixed before merging this branch.

  • cp313t-win_amd64: I've not investigated this issue yet, but I don't think free-threaded builds are used by many users at the moment, so I'd just disable this one, leaving free-threaded builds only of the other OSs.
  • cp37-macosx_x86_64: I was thinking to remove support for python 3.7 in the near future, if it is already a problem to maintain we could disable it in this PR (I mean, all 3.7 builds). Python 3.7 has been EOL for almost 2 years, I believe it makes just sense to stop supporting it.
  • cp38-macosx_arm64: It would be nice to fix this one, but if I recall correctly Apple Silicon was released after python 3.8, so all users on that platform should be on 3.9+. We could think to disable it if it's difficult to make it work.

Regarding linux on arm builds, it's definitely a step back to disable them. ARM is the standard platform on embedded devices, and it's gaining momentum also on server side, so I'd like to have working builds to cover this segment of users.

Let me know what do you think.

Alessio

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.

2 participants