ci: re-enable ffi check on 3.13 for PyConfig, ignore _PyCoLineInstrumentationData
#5065
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
Free threaded tests seem legitimately broken in async code, cc @ngoldbaum I'm going to try to reproduce locally. |
Member
Author
|
I can reproduce with |
Merged
newcomertv
pushed a commit
to newcomertv/pyo3
that referenced
this pull request
Apr 28, 2025
…mentationData` (PyO3#5065) * ci: re-enable ffi check on 3.13 for PyConfig, ignore `_PyCoLineInstrumentationData` * force 3.13 jobs to use latest 3.13.3
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
3.13.2 broke ffi-check for
PyConfigdue to ABI break upstream, should have been fixed in 3.13.3.Let's also ignore
_PyCoLineInstrumentationDatatemporarily to unblock CI, will be removed in #5064