-
Notifications
You must be signed in to change notification settings - Fork 79
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
chore: 3.13 support #703
chore: 3.13 support #703
Conversation
@@ -80,7 +83,7 @@ jobs: | |||
env: | |||
CIBW_TEST_REQUIRES: "pytest msgpack pyyaml tomli tomli_w" | |||
CIBW_TEST_COMMAND: "pytest {project}/tests" | |||
CIBW_BUILD: "cp38-* cp39-* cp310-* cp311-* cp312-*" | |||
CIBW_BUILD: "cp38-* cp39-* cp310-* cp311-* cp312-* cp13-*" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Usually pypa/cibuildwheel
minor version takes care of adding and removing EOL and new python versions. I think there is some handling for pre-release but don't remember how.
Could consider moving these to the pyproject.toml
to make it more easily reproducible and removing the explicit CIBW_BUILD
?
(Not in this PR, but a subsequent one when python 3.13 is working)
#if PY313_PLUS | ||
// Python 3.13 adds an extra argument to control whether to throw an error on overflow. | ||
// This happens by default in older versions, so simply match the behavior. | ||
out = _PyLong_AsByteArray((PyLongObject *)int128, buf, 16, 0, 0, 0, 1); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're not declaring int out
anymore.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…and passing one argument too many in both branches.
@mgorny @max-muoto I've put up #711 and I can confirm wheels can be built and tests pass on Python 3.13 |
Closing in favor of #711, thanks @edgarrmondragon! |
Fix issues detailed in #698