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

Python 3.13 support #797

Closed
2 of 7 tasks
nitzmahone opened this issue May 13, 2024 · 1 comment · Fixed by #808
Closed
2 of 7 tasks

Python 3.13 support #797

nitzmahone opened this issue May 13, 2024 · 1 comment · Fixed by #808

Comments

@nitzmahone
Copy link
Member

nitzmahone commented May 13, 2024

Now that Python 3.13.0b1 is out, time to get at least a 6.0.2 pre-release out the door with 3.13 support. Most everything is working, but there are a couple of deferred housekeeping things that I'm still finishing up...

  • Support for Cython 3.0+ (via conditional old_build_ext import)
  • Custom cibuildwheel with 3.13 support
  • Update CI.yaml to use dynamic matrix (eliminate extra copy for release)
  • Support for macos-14 GHA runner (native Apple Silicon, reduces need for our self-hosted runners)
  • Update libyaml Mac shared build to work with newer autoconf
  • Support for windows-2022 GHA runner
  • Update libyaml Windows shared build to run under VS2022
@Uzume
Copy link

Uzume commented May 18, 2024

In regard to "Support for Cython 3.0+ (via conditional old_build_ext import)", is a #731/#602 style "fix" (to get around cython/cython#4498) really a good idea? Wouldn't it be a better idea to move away from cython_sources, Cython.Distutils.build_ext/Cython.Distutils.old_build_ext and the deprecated distutils to the supported Cython.Build.build_ext? Cython likely means to drop support for those deprecated interfaces at some point (especially since python/cpython#92584). Wouldn't a #729 style fix (at build time only; see my comments there) be a better approach since Distributing Cython modules seems to be the recommended and supported method (and presumably is more unlikely to break in the future)?

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 a pull request may close this issue.

2 participants