Skip to content

Conversation

@lysnikolaou
Copy link

I've completed an auditing of the C extension modules and it does not appear to have any global state. Thus, we can signify that the extension does not rely on the GIL for thread safety, so that it's not dynamically reenabled when thrift.protocal.fastbinary is imported.

  • If a ticket exists: Does your pull request title follow the pattern "THRIFT-NNNN: describe my issue"?
  • Did you squash your changes to a single commit? (not required, but preferred)
  • Did you do your best to avoid breaking changes? If one was needed, did you label the Jira ticket with "Breaking-Change"?

I've completed an auditing of the C extension modules and it does
not appear to have any global state. Thus, we can signify that the
extension does not rely on the GIL for thread safety, so that it's
not dynamically reenabled when `thrift.protocal.fastbinary` is
imported.
@Jens-G Jens-G added the python label Jul 25, 2025
@lysnikolaou
Copy link
Author

Friendly ping on this. All of the CI failures appear to be unrelated.

@ngoldbaum
Copy link

@lysnikolaou can you see if the failures go away when you rebase?

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants