Skip to content

Conversation

@clin1234
Copy link
Contributor

No description provided.

@davidhewitt
Copy link
Member

I added full build, if you want to fixup merge conflict we can see what initial results are.

Co-authored-by: Bas Schoenmaeckers <[email protected]>
@bschoenmaeckers
Copy link
Member

You should bump cpython’s max-version in pyo3-ffi/cargo.toml to 1.15.

@Tpt
Copy link
Contributor

Tpt commented Oct 22, 2025

You should bump cpython’s max-version in pyo3-ffi/cargo.toml to 1.15.

cpython 3.15 C-API is I think still moving, wouldn't it better to keep the error message and use UNSAFE_PYO3_SKIP_VERSION_CHECK until the API is stabilized? I am a bit afraid we ship a PyO3 version that end up broken on cpython 3.15 released versions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants